fix(host): support RFC-0023 signing callbacks - #145
Conversation
Bundle Size ReportChunks over 500 KB:
All files
Commit: bf73296 |
⚡ Performance Report
|
|
This is a Nova-side outage and not a dot.li test failure. Re-run Logs: https://github.com/paritytech/dotli-community/actions/runs/30880865836 |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
❌ E2E Product suite failed on Failed tests:
Logs: https://github.com/paritytech/dotli-community/actions/runs/30904235928 |
Summary
AutoSigningKeyvalues in opaque, encrypted core-storage slotsAutoSigningSignVrfrequestsCoreStorageKeyand confirmation types directlyAuthorization behavior
RFC-0023 has two paths:
AutoSigninggrant signs locally without a promptSign VRF Transcriptconfirmation; only after approval does the pairing-host runtime forward it to the paired Account Holder, which presents its own confirmation and signsThe Dotli review shows the requesting product, signer, transcript label, and transcript item count. Cross-product requests always use this confirmed remote path.
Merge prerequisite
Merge the companion release PR and publish
@parity/truapi@0.7.0plus@parity/truapi-host@0.4.0. Then update this PR's dependency versions and lockfile before merging. Backward compatibility with the currently published@parity/truapi-host@0.3.0is intentionally not provided.Tests
Using the linked RFC-0023 TrUAPI checkout:
sign_vrfauthorization tests: 5 passedmake e2e-dotli: 44 successful, 21 expected/allowlisted outcomes;Account/sign_vrfshowed the DotliSignconfirmation first, then passed through the paired signing-host CLI approval and returned a signatureCompanion release PR
@parity/truapi@0.7.0,@parity/truapi-host@0.4.0