Add a first draft for core tech address/transaction/block
#205
Conversation
docs/core-tech/address.md
Outdated
| sidebar_label: Address | ||
| --- | ||
|
|
||
| An Alephium address is an identifier used to interact with an Alephium network. Addresses can be user-controlled or deployed through a contract. |
There was a problem hiding this comment.
[Nit] "An Alephium address represents a user or a contract within the Alephium network."
docs/core-tech/address.md
Outdated
|
|
||
| Alephium has two address types: | ||
|
|
||
| * Asset: corresponding to a public/private key pair. Controlled by the private key |
There was a problem hiding this comment.
Asset address type includes P2SH, I guess strictly speaking it might not be controlled by private keys.
docs/core-tech/address.md
Outdated
| * Receive, hold and send ALPH and tokens | ||
| * Interact with deployed contracts | ||
|
|
||
| Assets can have three different form: |
There was a problem hiding this comment.
| Assets can have three different form: | |
| Assets can have three different forms: |
docs/core-tech/address.md
Outdated
|
|
||
| * P2C: Pay-to-Contract | ||
|
|
||
| ## Asset address |
There was a problem hiding this comment.
I suppose this paragraph is only valid for P2PKH.
docs/core-tech/address.md
Outdated
|
|
||
| An asset address is derived from a cryptographic pair of public and private keys, using the same [secp256k1's elliptic curve](https://en.bitcoin.it/wiki/Secp256k1) as bitcoin. | ||
| Those keys play a crucial role in validating the authenticity of a transaction and safeguarding against fraudulent activities. | ||
| The private key is used to sign the transactions, as the address is derived from the public key, anyone can validate the signature. |
There was a problem hiding this comment.
[Nit] It can be used to sign any messages, including transactions.
docs/core-tech/block.md
Outdated
|
|
||
| ## Prerequisites | ||
|
|
||
| Understanding of a [Transaction](/core-tech/transaction) is a plus. |
There was a problem hiding this comment.
[Nit] Since this is under Prerequisites, perhaps update is a plus to is required.
docs/core-tech/block.md
Outdated
|
|
||
| ## Overview of a Block | ||
|
|
||
| Each Alephium block includes various components, such as the timestamp of creation, a record of transactions, and a reference to the dependencies blocks. Additionally, it incorporates the solution to the mining puzzle that is unique to each block, so the network can easily verify its correctness. While multiple valid solutions may exist for a given block, only one needs to be discovered to consider the block solved. As an incentive for solving each block, miners are rewarded with new generated ALPH. |
There was a problem hiding this comment.
- new generated ALPH -> newly generated ALPH.
- a reference to the dependencies blocks -> references to the dependent blocks
docs/core-tech/transaction.md
Outdated
| sidebar_label: Transaction | ||
| --- | ||
|
|
||
| A transaction refers to the act of transferring an entity from one address to another within the network. It is a fundamental operation that enables the exchange of Alephium's native cryptocurrency ALPH, or any other tokens or contract data. |
There was a problem hiding this comment.
Other than the value transfer aspect of the transaction, we should probably capture the execution of the smart contract as well.
There was a problem hiding this comment.
what about:
A transaction in Alephium denotes the process of transferring an entity, such as Alephium's native cryptocurrency ALPH, tokens, or contract data, from some addresses to other ones within the network. Beyond facilitating the exchange of value, transactions also play a pivotal role in executing smart contracts. These contracts allow for the implementation of programmable logic, enabling a diverse range of functionalities and decentralized applications on the Alephium blockchain.
Totally no written with ChatGPT 🙊 🙈 🙉
There was a problem hiding this comment.
Maybe replace entity by asset ? Data can be considered an asset no ? It's just the word entity feels weird to me in this context.
|
|
||
| A transaction typically includes the following components: | ||
|
|
||
| * Inputs: list of previous unspent outputs, transaction's signatures will prove that those inputs can be spent. |
There was a problem hiding this comment.
yeah that's why I introduce with A transaction typically, I was not thinking of going into advanced stuff. It should be covered in other docs I think.
docs/core-tech/transaction.md
Outdated
| * Transaction Fee: A small amount of cryptocurrency paid by the sender to to get his transaction included in a block. | ||
|
|
||
| When a transaction is created, it undergoes a validation process to ensure that the inputs have sufficient funds, the transaction is properly signed, UTXO model is respected and other relevant conditions are met. | ||
| Once validated, the transaction is added to a [block](/core-tech/block) and subsequently added to the [BlockFlow](/core-tech/blockflow-and-sharding), becoming a permanent part of Alephium's history. |
There was a problem hiding this comment.
Q: do we say a block is added to blockflow, since blockflow is an algorithm?
There was a problem hiding this comment.
should we say something like: and subsequently added to one of our sharded blockchain?
There was a problem hiding this comment.
The blockchain in which the bloc is added is not sharded (it's a single chain) so maybe "subsequently added to one of the blockchain of the Alephium's network". You could also add at the end "according to the groups of the addresses involved in the transaction".
|
@tdroxler I let you check if it can now be merged :) |
|
|
The latest document has covered this |
Here is a very first start to add those 3 pages, let's discuss and see if we want more for this first version