Construct transactions with other parties
Opened this issue · 1 comments
Hi there!
First let me say that this wallet is amazing! Great work and kudos to the team for their ongoing effort, you certainly have my support. All the essentials are there, but can we do more?
Well I got an idea that would be really helpful for the community and would really provide addition value to the whole ecosystem. I propose a section in the wallet for constructing transactions with UTxO not from the imported wallet. In addition these transactions can be exported and imported from the wallet to CBOR (just like we already can). This to facilitate trade of the most basic form.
An example, say that I know someone that holds an native token X. I search the UTxO that contains that token X and construct a transaction that consumed it and 1 or more UTxO's from my wallet. I then sign this transaction and export it. The CBOR file is send via any communication channel desirable to the owner of the UTxO that holds the token X. They can import the transaction and view it (ALERT: a fair warning to really make this viewing insightful to prevent unwanted trades). If they agree with the trade they can sign it to make it valid and send it.
Just simple trade between parties that know each other without the need of smart contracts. This will greatly decrease the burden on the blockchain by not using the space allocated for plutus scripts in blocks for mundane trades. Moreover, I hope that in the future a market place is build around this principle such that bidding can be free (a partially signed transaction if worth noting). This market place would further decrease the burden on the chain pulling on-chain calculations further off-chain (only settlement remains). This market place could be made censor resistant via IPFS or something build on the matrix protocol. But this is the next step.
Looking forward to your reply of my suggestion! I know that it is viable since the wallet already has some of these features :)
Hi @fermatspace, this is something we need to discuss with the entire team regarding if to implement and if so in which way. Thanks for the suggestion, we will consider this for sure, but are keeping in mind this would only be useful for a few select users.