Skip to content

Add guide for debugging entropy callbacks #365

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 16, 2024
Merged

Add guide for debugging entropy callbacks #365

merged 2 commits into from
Jul 16, 2024

Conversation

jayantk
Copy link
Contributor

@jayantk jayantk commented Jul 10, 2024

No description provided.

Copy link

vercel bot commented Jul 10, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
documentation ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 16, 2024 3:35pm

Entropy will callback your contract with the generated random number once the request is fullfilled by the provider.
Integrations simply call an on-chain function to request a random number from Entropy.
This function takes a random number that you have generated off-chain and returns a sequence number.
Entropy will then callback your contract with the generated random number once the request is fullfilled by the provider.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

drive-by simplification of the text here

export ENTROPY_ADDRESS=0x5744Cbf430D99456a0A8771208b674F27f8EF0Fb
```

Three of the arguments can be retrieved from the request transaction's event logs.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we give a small explanation here about these arguments?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm trying to stick to the diataxis guideline to avoid explanation in how-to guides. I also think anyone reading this guide will know what these are (because they wrote the code to integrate the software in the first place)

@jayantk jayantk merged commit 813474c into main Jul 16, 2024
4 checks passed
@jayantk jayantk deleted the debug_docs branch July 16, 2024 16:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants