-
GRIN uses a timelock. What additional functionality does BEAM add to this timelock?
BEAM also includes the ability to specify an upper time limit, after which the transaction can no longer be included in a block. This feature means that a party can be sure that if a transaction is not included in a block on the main blockchain after a certain time then it will never appear. -
BEAM proposes to improve scalability by letting users recycle transaction kernels. How will they encourage users to use this feature?
BEAM has proposed a scheme to reuse these transaction kernels to validate subsequent transactions. In order to incentivize transactions to be built in this way, BEAM includes a fee refund model for these types of transactions. -
In a GRIN transaction, both parties must be online at the same time. How does BEAM allow this to be done asynchronously?
BEAM has implemented a Secure Bulletin Board System (SBBS) that is run on BEAM full-nodes to allow for asynchronous negotiation of transactions. -
How does BEAM plan to support one-sided transactions?
BEAM also plans to support one-sided transactions where the payee in a transaction who expects to be paid a certain amount can construct their half of the transaction and send this half-constructed transaction to the payer.BEAM solves this problem by using a process it calls kernel fusion , whereby a kernel can include a reference to another kernel so that it is only valid if both kernels are present in the transaction. In this way, the payee can build their half of the transaction with a secret blinding factor and a kernel that compensates for their blinding factor, which must be included when the payer completes the transaction.
