Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

CIP-0106? | Web-Wallet Bridge - Multisig wallets #617

Merged
merged 30 commits into from
Jun 26, 2024
Merged
Changes from 1 commit
Commits
Show all changes
30 commits
Select commit Hold shift + click to select a range
0db056f
Initial draft completed
leo42 Nov 11, 2023
81780e1
Merge branch 'cardano-foundation:master' into master
leo42 Nov 11, 2023
2f80311
Update CIP-130/README.md
leo42 Nov 11, 2023
2a8ca30
Update CIP-130/README.md
leo42 Nov 11, 2023
48ff4c2
renaming CPI folder
leo42 Nov 11, 2023
7ecb1bc
Update CIP-XXXX/README.md
leo42 Nov 11, 2023
92732d3
remove exes whitespaces
leo42 Nov 11, 2023
1b7c753
Rework as a CIP-30 Extension
leo42 Nov 14, 2023
f934813
small improvment
leo42 Nov 27, 2023
d014274
standardising title with wallet extension CIPs
rphair Dec 6, 2023
2561e4e
applying official CIP number 106
rphair Dec 12, 2023
ec1bdfc
Merge branch 'master' of https://github.com/leo42/CIPs
leo42 Dec 13, 2023
7d9cb6d
Rename and mark reference implementation as complete
leo42 Dec 13, 2023
aaa736a
rename
leo42 Dec 13, 2023
cfc5318
Merge branch 'cardano-foundation:master' into master
leo42 Apr 15, 2024
adb8da1
Update CIP-0106/README.md
leo42 May 15, 2024
ab9e1ef
Update CIP-0106/README.md
leo42 May 15, 2024
9d6a57f
Update CIP-0106/README.md
leo42 Jun 5, 2024
e2ab1fc
remove duplicate sections
leo42 Jun 6, 2024
dc00f1b
Update README.md
leo42 Jun 6, 2024
7292e1c
Update README.md
leo42 Jun 6, 2024
f0e298b
add namespacing
leo42 Jun 6, 2024
1e70fa9
Update README.md
leo42 Jun 6, 2024
9a8db7f
needs seminal pull request as Discussion
rphair Jun 11, 2024
ce033b7
Add implementors , remove rational for required data
leo42 Jun 12, 2024
483b8c8
Update CIP-0106/README.md
leo42 Jun 12, 2024
1d13e70
Update README.md
leo42 Jun 12, 2024
fd6e5cb
Changed Removed Endpoints to Disabled Endpoints
leo42 Jun 13, 2024
a9f2670
very minor formatting: white space justification
rphair Jun 22, 2024
bb015c5
fix spelling mistake in CIP title
rphair Jun 22, 2024
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
Prev Previous commit
Next Next commit
Update README.md
  • Loading branch information
leo42 committed Jun 12, 2024
commit 1d13e7073301793d2a7e3f54aeea3709f931d27e
11 changes: 7 additions & 4 deletions CIP-0106/README.md
Original file line number Diff line number Diff line change
@@ -22,10 +22,13 @@ This document describes a CIP-30 extension allowing webpages (i.e. dApps) to int
In order to facilitate future dApp development, we will need a way for dApps to communicate with multisig wallets, given the unique complexities of native script based addresses. Special provisions need to be made to make the connector compatible with them.

Specifically, apps building transactions need to be able to get the following information from the wallet:
- Script descriptor
- Script Requirements list
- Collateral donator (since native script based addresses cannot provide collateral for transactions)

- Script descriptor
- Any transaction consuming a UTXO from a Plutus-based address must attach the corresponding script.
- `ScriptRequirements`
- The `TxContext` that is required to be able to validate the transaction. It encompasses all the possible combinations of requirements for the transaction to be valid, as such it is represented by an array of `ScriptRequirement` objects.
- Change Datum
- The datum that will be used as the change output for the transaction. This is required for wallets based on Plutus V2 and before, as the change output must contain a datum to be valid and spendable.

Additionally, apps need to be able to submit a transaction to the wallet for signing in an asynchronous manner, as gathering of signatures can take a long time and each wallet provider will have its own way of handling this process.

Finally, the signTx() and signData() endpoints will have to be disabled when using this extension since they are not compatible with native script based addresses.