mirror of
https://github.com/serai-dex/serai.git
synced 2024-12-25 04:59:31 +00:00
8ca90e7905
* Initial work on an In Inherents pallet * Add an event for when a batch is executed * Add a dummy provider for InInstructions * Add in-instructions to the node * Add the Serai runtime API to the processor * Move processor tests around * Build a subxt Client around Serai * Successfully get Batch events from Serai Renamed processor/substrate to processor/serai. * Much more robust InInstruction pallet * Implement the workaround from https://github.com/paritytech/subxt/issues/602 * Initial prototype of processor generated InInstructions * Correct PendingCoins data flow for InInstructions * Minor lint to in-instructions * Remove the global Serai connection for a partial re-impl * Correct ID handling of the processor test * Workaround the delay in the subscription * Make an unwrap an if let Some, remove old comments * Lint the processor toml * Rebase and update * Move substrate/in-instructions to substrate/in-instructions/pallet * Start an in-instructions primitives lib * Properly update processor to subxt 0.24 Also corrects failures from the rebase. * in-instructions cargo update * Implement IsFatalError * is_inherent -> true * Rename in-instructions crates and misc cleanup * Update documentation * cargo update * Misc update fixes * Replace height with block_number * Update processor src to latest subxt * Correct pipeline for InInstructions testing * Remove runtime::AccountId for serai_primitives::NativeAddress * Rewrite the in-instructions pallet Complete with respect to the currently written docs. Drops the custom serializer for just using SCALE. Makes slight tweaks as relevant. * Move instructions' InherentDataProvider to a client crate * Correct doc gen * Add serde to in-instructions-primitives * Add in-instructions-primitives to pallet * Heights -> BlockNumbers * Get batch pub test loop working * Update in instructions pallet terminology Removes the ambiguous Coin for Update. Removes pending/artificial latency for furture client work. Also moves to using serai_primitives::Coin. * Add a BlockNumber primitive * Belated cargo fmt * Further document why DifferentBatch isn't fatal * Correct processor sleeps * Remove metadata at compile time, add test framework for Serai nodes * Remove manual RPC client * Simplify update test * Improve re-exporting behavior of serai-runtime It now re-exports all pallets underneath it. * Add a function to get storage values to the Serai RPC * Update substrate/ to latest substrate * Create a dedicated crate for the Serai RPC * Remove unused dependencies in substrate/ * Remove unused dependencies in coins/ Out of scope for this branch, just minor and path of least resistance. * Use substrate/serai/client for the Serai RPC lib It's a bit out of place, since these client folders are intended for the node to access pallets and so on. This is for end-users to access Serai as a whole. In that sense, it made more sense as a top level folder, yet that also felt out of place. * Move InInstructions test to serai-client for now * Final cleanup * Update deny.toml * Cargo.lock update from merging develop * Update nightly Attempt to work around the current CI failure, which is a Rust ICE. We previously didn't upgrade due to clippy 10134, yet that's been reverted. * clippy * clippy * fmt * NativeAddress -> SeraiAddress * Sec fix on non-provided updates and doc fixes * Add Serai as a Coin Necessary in order to swap to Serai. * Add a BlockHash type, used for batch IDs * Remove origin from InInstruction Makes InInstructionTarget. Adds RefundableInInstruction with origin. * Document storage items in in-instructions * Rename serai/client/tests/serai.rs to updates.rs It only tested publishing updates and their successful acceptance.
38 lines
1.2 KiB
Markdown
38 lines
1.2 KiB
Markdown
# Ethereum
|
|
|
|
### Addresses
|
|
|
|
Ethereum addresses are 20-byte hashes.
|
|
|
|
### In Instructions
|
|
|
|
Ethereum In Instructions are present via being appended to the calldata
|
|
transferring funds to Serai. `origin` is automatically set to the party from
|
|
which funds are being transferred. For an ERC20, this is `from`. For ETH, this
|
|
is the caller.
|
|
|
|
### Out Instructions
|
|
|
|
`data` is limited to 512 bytes.
|
|
|
|
If `data` is provided, the Ethereum Router will call a contract-calling child
|
|
contract in order to sandbox it. The first byte of `data` designates which child
|
|
child contract to call. After this byte is read, `data` is solely considered as
|
|
`data`, post its first byte. The child contract is sent the funds before this
|
|
call is performed.
|
|
|
|
##### Child Contract 0
|
|
|
|
This contract is intended to enable connecting with other protocols, and should
|
|
be used to convert withdrawn assets to other assets on Ethereum.
|
|
|
|
1) Transfers the asset to `destination`.
|
|
2) Calls `destination` with `data`.
|
|
|
|
##### Child Contract 1
|
|
|
|
This contract is intended to enable authenticated calls from Serai.
|
|
|
|
1) Transfers the asset to `destination`.
|
|
2) Calls `destination` with `data[.. 4], serai_address, data[4 ..]`, where
|
|
`serai_address` is the address which triggered this Out Instruction.
|