Multisig Functionality

[tse-lao]

@tse-lao

• [ ] Use the create Multisig function in the useContract to create a new multisig. When the multisig is going to get created you need to find from the transaction hash the internal transaction and then the address of the multisig use this one ⇒ https://docs.polygonscan.com/v/mumbai-polygonscan/api-endpoints/accounts#get-internal-transactions-by-transaction-hash

Option 1:

• [x] Create then a polybase collection that is going to keep track of all the multisigs and their owners so we can display that in the user profile

• [x] Each multisig address needs to have in polybase their transaction proposals like

  Collection { MultisigAddress , proposalID , transactionData of the proposal }
  Collection { proposalID , multisigOwnerAddress, Signature }
  
  If a proposal ID has more than n signatures then we can execute 
  the proposal transaction. n is defined on multisig creation needs to be
  <= numberOFmultisig owners and tells how many need to agree or sign a transaciton
  for this transaction to be executed on the smart wallet
  
  Thats why we need to store in polybase for each multisig proposal 
  all the signatures. If the signatures are >= n then we can show in the UI that 
  any multisig owner can execute that transaction

Option 2: Go for this one first. @nijoe1

• [x] Put everything on tableland
• [x] Perform the signatures on-chain

[tse-lao]

@nijoe1 so you want to keep track of mutations in the contracts with Polybase as helpers, but all the functionalities should be verifiable in the contract itself. Why do we need to use Polybase here and not just push the link automatically towards a tableland table based on the execution of the contract?