-
Notifications
You must be signed in to change notification settings - Fork 1
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.
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
Build many TXIntents for batch of TX applying Security Shield #349
base: main
Are you sure you want to change the base?
Build many TXIntents for batch of TX applying Security Shield #349
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #349 +/- ##
==========================================
- Coverage 92.64% 92.46% -0.19%
==========================================
Files 1180 924 -256
Lines 26658 23986 -2672
Branches 77 77
==========================================
- Hits 24698 22178 -2520
+ Misses 1949 1797 -152
Partials 11 11
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
1086b4c
to
d014fee
Compare
… due to 'static lifetime requirement.
…ail due to 'static lifetime requirement. (last commit msg meant I commit the failed state.)
impl GetEntityAddressByAccessControllerAddress for Profile { | ||
fn get_securified_entity_by_access_controller_address( | ||
&self, | ||
address: AccessControllerAddress, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will use RET to analyze the "apply shield" manifest and we will get a classification containing either an address of an Unsecurified Persona or an Unsecurified Account being securified or the address of an AcccessController of an already securified entity being updated - in case of the latter we will need to lookup the Account/Persona using that AccessControllerAddress
} | ||
} | ||
|
||
fn hacky_tmp_entities_applying_shield( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
everything named hacky_
will be removed once #373 is merged and we can get those addresses from the manifest using RETs analysis
Jira ABW-4012
Note
Does not sign -
SigningManager
is to be implemented in future PRDoes not add any TXBatchQueue, the queue is to be implemented in future PR
Changes
Add
ApplySecurityShieldCommitting
implemented for SargonOS - usingApplyShieldTransactionsCommitter
"manager". Input is aVec
of:estimated_xrd_fee
hosts will have fetched when doing the preview.Important
The API/DTOs passed between host and Sargon is non-final, this is just a first iteration. Furthermore we might expose more methods, e.g. logic for XRD balance validation when selecting payer, which this PR introduces code for. Once we are more sure about the API - from reviews, we will
UniFFI
export the needed APIs.Steps
Other minor
AddressOfVaultOrAccount
(used by this PR)TryFrom<$UNION> for $VARIANT
access_controller_address
directly but ratheraddresses
of a new typeAddressesOfAccessController
which containsaccess_controller_address
andxrd_vault_address: VaultAddress
.TryFrom<Account> for SecurifiedAccount
and vice versa for Securified/Persona.TryFrom<Account> for UnsecurifiedAccount
and vice versa for Unsecurified/Persona.