Add a "technical specs" page. Fixes #780 #894
Conversation
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/blockstack/blockstack-docs/patw2ifa8 |
Blockstack DocumentationBlockstack docs have been deployed with Vercel using the code from this PR! 📝 Changed routes:
Built with commit aa67079. |
|
@agraebe @jeffdomke before I spend more time on this, want to get your quick take on whether this is directionally correct -- does this address what you in mind? |
|
looks great - this is what I had in mind |
diwakergupta
changed the title
|
|
||
| ## Stacking | ||
|
|
||
| - Stacking works in 2 phases |
There was a problem hiding this comment.
should we mention that stacking is essentially a clarity contract & maybe linking to the stacking contract references would make sense?
| 3. _sending account_ is the account that identifies who is currently executing the transaction: this can change as a transaction executes via the `as-contract` Clarity function | ||
| - Two types of authorizations: standard authorization is where originating account is the same as paying account. _Sponsored_ authorization is where originating account and paying account are distinct. For instance, developers or service providers could pay for users to call their smart-contracts. | ||
| - For sponsored authorization, first a user signs with the originating account and then a sponsor signs with the paying account. | ||
| - Transaction encoding is described [here](https://github.com/blockstack/stacks-blockchain/blob/master/sip/sip-005-blocks-and-transactions.md#transaction-encoding). |
There was a problem hiding this comment.
and here, probably easier to link to: https://github.com/blockstack/stacks-blockchain/blob/master/sip/sip-007-stacking-consensus.md#stacker-delegation
There was a problem hiding this comment.
Why? This bullet is about encoding, not delegation
There was a problem hiding this comment.
Sorry, I meant to link to: https://docs.blockstack.org/stacks-blockchain/transactions#encoding
| - Two types of authorizations: standard authorization is where originating account is the same as paying account. _Sponsored_ authorization is where originating account and paying account are distinct. For instance, developers or service providers could pay for users to call their smart-contracts. | ||
| - For sponsored authorization, first a user signs with the originating account and then a sponsor signs with the paying account. | ||
| - Transaction encoding is described [here](https://github.com/blockstack/stacks-blockchain/blob/master/sip/sip-005-blocks-and-transactions.md#transaction-encoding). | ||
| - Transaction signing and verification are described [here](https://github.com/blockstack/stacks-blockchain/blob/master/sip/sip-005-blocks-and-transactions.md#transaction-signing-and-verifying). |
There was a problem hiding this comment.
| 3. _sending account_ is the account that identifies who is currently executing the transaction: this can change as a transaction executes via the `as-contract` Clarity function | ||
| - Two types of authorizations: standard authorization is where originating account is the same as paying account. _Sponsored_ authorization is where originating account and paying account are distinct. For instance, developers or service providers could pay for users to call their smart-contracts. | ||
| - For sponsored authorization, first a user signs with the originating account and then a sponsor signs with the paying account. | ||
| - Transaction encoding is described [here](https://github.com/blockstack/stacks-blockchain/blob/master/sip/sip-005-blocks-and-transactions.md#transaction-encoding). |
There was a problem hiding this comment.
Why? This bullet is about encoding, not delegation
Mostly adding links.
There was a problem hiding this comment.
left one note, but looking great overall! approving so we can merge once ready
Thanks @diwakergupta 🙏
@GinaAbrams here you go: https://docs.blockstack.org/stacks-blockchain/technical-specs |
|
Woot thanks @diwakergupta! |
No description provided.