mirror of
https://github.com/dashpay/dash.git
synced 2024-12-25 12:02:48 +01:00
82310b0984
## Issue being fixed or feature implemented RPC `getassetunlockstatuses` is now accepting an extra optional parameter `height`. When a valid `height` is passed, then the RPC returns the status of AssetUnlock indexes up to this specific block. (Requested by Platform team) ## What was done? Note that in order to avoid cases that can lead to deterministic result, when `height` is passed, then the only `chainlocked` and `unknown` outcomes are possible. ## How Has This Been Tested? `feature_asset_locks.py` was updated. ## Breaking Changes n/a ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_ --------- Co-authored-by: Konstantin Akimov <knstqq@gmail.com> Co-authored-by: UdjinM6 <UdjinM6@users.noreply.github.com>
696 B
696 B
Added RPC
getassetunlockstatuses
RPC allows fetching of Asset Unlock txs by their withdrawal index. The RPC accepts an array of indexes and an optional block height. The possible outcomes per each index are:chainlocked
: If the Asset Unlock index is mined on a ChainLocked block or up to the given block height.mined
: If no ChainLock information is available for the mined Asset Unlock index.mempooled
: If the Asset Unlock index is in the mempool.unknown
: If none of the above are valid.
Note: If a specific block height is passed on request, then only chainlocked
and unknown
outcomes are possible.
Note: This RPC is whitelisted for the Platform RPC user.