Support P2SH Style MultiSign Script about ckb-system-scripts HOT 3 CLOSED

Suggest change the multisign_script to a more general option, let it works for both multisig and single signature.

We can easily extend it to support check tx since field (or other features), I am thinking this for a long time we should support since in system lock script.

For example multi=2/3,since=1d, represents the multisig is a 2 of 3, and the tx to spent this cell should be confirmed at least 1 day later than this cell created. We can also use position to indicates the option but then it will be relatively hard to upgrade or extend.

We can support a few basic since option:

• 1d, 1y, 1w, 1h we can spend this cell after X day/year/week/hours.
• 1b, 1e we can spend cell after 1 block, or 1 epoch.
• Add ! before the value to indicate value represent absolute time. for example: !1000b, !1568186924s.

from ckb-system-scripts.

I think since field should be a initiator-determined parameter, which means it is the transaction initator who should set it, not the receiver. And the address is a receiver-determined parameter. It is inappropriate to include since in address.

System scripts is used for most of users. If they use addresses with since, different since will generate different addresses even with the same PK. It is hard to explain why they cannot find all transactions on CKB Explorer for the same PK.

from ckb-system-scripts.

I think since field should be a initiator-determined parameter, which means it is the transaction initator who should set it

the lock script can also constraint when a cell can be spent by verify tx since, it works similarly as Bitcoin script.

https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki#escrow-with-timeout

different since will generate different addresses even with the same PK.

Most time, users will ignore the since field, I am also curios how a multisig user can find txs?

from ckb-system-scripts.