Skip to content
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.

Sign up for GitHub

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

Account ownership testaments #8

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
+16 −2
Open

Account ownership testaments #8

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
5854826
Added draft for claim
lucasvo Feb 10, 2021
bc7ffee
Cleanup
lucasvo Feb 10, 2021
6db56f4
clarified timestamp
lucasvo Feb 10, 2021
b3ea3b6
Removing redundant `source` field in `AccountClaim`
lucasvo Oct 5, 2021
f622912
Merge branch 'master' into claim
lucasvo Oct 5, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,7 @@ Where message `type` must be one of:
- `4`: `Transact`
- `5`: `RelayTo`
- `6`: `RelayedFrom`
- `7`: `AccountClaim`

Within XCM, there is an internal datatype `Order`, which encodes an operation on the holding account. It is defined as:

Expand Down Expand Up @@ -222,7 +223,19 @@ Remove the asset(s) (`assets`) from holding and send a `WithdrawAsset` XCM messa
be executed on them. There will typically be only one valid location on any given asset/chain combination.
- `effects: Vec<Order>`: The orders to execute on the assets once withdrawn *on the reserve location*.

<<<<<<< HEAD
Errors:
=======
### `AccountClaim`
Sends a claim verified to be from the `source` to the `destination` on the parachain. It has an `expiration` timestamp and a `scope` used to define the scope under which such a `claim` is made. A chain should only send such a claim if it is verified to have been intended to be sent by the `source`. It facilitates authentication across parachains.

- `source: MultiLocation`
- `destination: MultiLocation`
- `timestamp: Compact<u48>`
Copy link
Contributor

Choose a reason for hiding this comment

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

How is timestamp going to be used? Upon receive the message, the dest chain should just transfer the assets into the destination account immediately.

Copy link
Author

Choose a reason for hiding this comment

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

This is not used for assets but merely indicates the validity of the claim. In the crowdloan example it would you would first sign an extrinsic on the relay chain instructing it to send a claim to the parachain with such a claim and an expiration date. Until such a timestamp has passed, the parachain would allow the user to then submit an extrinsic to withdraw their reward from the destination account.

- `scope: Vec<u8>`

## `MultiAsset`: Universal Asset Identifiers
>>>>>>> a1a8822 (Added draft for claim)

### `InitiateTeleport`

Expand Down