docs: sb/extend auditor docs on AssetTracker component #4522
Conversation
|
|
||
| There are three types of asset trackers: | ||
|
|
||
| - `L1AssetTracker`. It took over the job of tracking chain balances on L1, that was previosuly held by `L1NativeTokenVault`. Note that due to costs, it does not support interop. |
There was a problem hiding this comment.
What about when we'll have L1 interop support (v31?)?
There was a problem hiding this comment.
Unlikely in v31, since the same reasoning about costs applies. Most likely it will require full ZK-based asset tracker for L1 support
There was a problem hiding this comment.
Is that not a blocker for stage 1? If we're not able to "catch" an in-flight interop transfer started on L2-A on L1
There was a problem hiding this comment.
Receiving interop may indeed be a blocker for stage1, but it will not be supported in v30 anyway.
There was a problem hiding this comment.
v30 true, but in v31 we planned to have stage1, so that's why I brought it up initially
docs/src/specs/contracts/bridging/asset_tracker/asset_tracker.md
Outdated
Show resolved
Hide resolved
docs/src/specs/contracts/bridging/asset_tracker/asset_tracker.md
Outdated
Show resolved
Hide resolved
docs/src/specs/contracts/bridging/asset_tracker/asset_tracker.md
Outdated
Show resolved
Hide resolved
docs/src/specs/contracts/bridging/asset_tracker/asset_tracker.md
Outdated
Show resolved
Hide resolved
docs/src/specs/contracts/bridging/asset_tracker/asset_tracker.md
Outdated
Show resolved
Hide resolved
|
|
||
| However, for migration-related messages for the ease of implementation we used the `migrationNumber` and `assetMigrationNumber`: An asset-migrating message can be only processed on L1 once, since to process it, the carried `migrationNumber` needs to be greater than the current `assetMigrationNumber`. | ||
|
|
||
| TODO: the current system allows for some of the old token withdrawals to never get finalized, this is bad, we'll have to rework it. |
There was a problem hiding this comment.
we'll have to rework it
OOS of v30? They will be finalizeable once we fix, but until then some of the old token withdrawals might be infinitely stuck?
There was a problem hiding this comment.
It should be inside v30 IMO
docs/src/specs/contracts/bridging/asset_tracker/asset_tracker.md
Outdated
Show resolved
Hide resolved
Co-authored-by: 0xValera <[email protected]>
…extend-auditor-docs
3 participants
What ❔
Why ❔
Is this a breaking change?
Operational changes
Checklist
zkstack dev fmtandzkstack dev lint.