-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Conversation
@cryptogosu is attempting to deploy a commit to the Solana Team on Vercel. A member of the Team first needs to authorize it. |
c28370e
to
686bb68
Compare
686bb68
to
ad42e05
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is super helpful!
47fa6ed
to
d4cda94
Compare
@jstarry Updated all documentation based on your suggestions. |
|
||
[Source Documentation](https://solana-labs.github.io/solana-web3.js/classes/NonceAccount.html) | ||
|
||
Normally a transaction is rejected if a transaction's `recentBlockhash` field is too old. To provide for certain custodial services, Nonce Accounts are used. Transactions created by a Nonce Account do not expire because they start with an `AdvanceNonceAccount` instruction, which updates the Nonce Account with an up-to-date `recentBlockhash`. This on-chain `recentBlockhash` is then used in the Nonce Account's transaction. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Normally a transaction is rejected if a transaction's `recentBlockhash` field is too old. To provide for certain custodial services, Nonce Accounts are used. Transactions created by a Nonce Account do not expire because they start with an `AdvanceNonceAccount` instruction, which updates the Nonce Account with an up-to-date `recentBlockhash`. This on-chain `recentBlockhash` is then used in the Nonce Account's transaction. | |
Normally a transaction is rejected if a transaction's `recentBlockhash` field is too old. To provide for certain custodial services, Nonce Accounts are used. Transactions which use a `recentBlockhash` captured on-chain by a Nonce Account do not expire as long at the Nonce Account is not advanced. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wish that the most important classes came first and the others were grouped by category. For example, starting off with Authorized
makes it feel that it's a foundational important thing to learn, but it's really just a detail of how the stake program. How about splitting some of these classes into categories like "General", "Staking", etc
Added web3 reference guide Added web3 reference guide
d4cda94
to
b9e4855
Compare
@jstarry I updated the order and format to have General and Staking. I also removed Let me know what you think about the new format. |
Looks much better thanks! |
Added web3 reference guide Added web3 reference guide (cherry picked from commit b16f2da)
Added web3 reference guide Added web3 reference guide
Added web3 reference guide Added web3 reference guide
This reverts commit c43a3e1.
Problem
Web3 was lacking a reference guide, and many ask for it in the support discord
Summary of Changes
Added web3 reference guide to the docs