Beam Unique Features - Reading Assignment

[Mihir23]

1. BEAM adds the ability to specify an upper time limit for a transaction. After the time limit, the transaction can no longer be included in a block. This feature assures parties that after a certain time, the transaction will never appear.

2. BEAM incorporates a fee refund model that incentivizes these types of transactions.

3. It implements a Secure Bulletin Board System (SBBS) that runs asynchronously on full-nodes in the network.

4. One-sided transactions are not possible on the normal Mimblewimble system because it involves trusting the counterparty with the blinding factor. To solve this, BEAM implemented a process called kernel fusion, where a kernel has a reference to another. The transaction will only be valid if both kernels are present within it.

[bbss]

1. BEAM also includes the ability to also 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, it will never appear.

2. BEAM includes a fee refund model for such transactions.

3. BEAM has implemented a Secure Bulletin Board System (SBBS) that is run on BEAM full-nodes to allow for asynchronous negotiation of transactions.

4. BEAM adds a process called kernel fusion.

[kylemoore8]

1. BEAM includes the ability to also specify an upper time limit.

2. Beam incentivises this feature with a refund model for the fees.

3. BEAM implemented a Secure Bulletin Board System that is run on BEAM’s full-nodes to allow for asynchronous negotiation of transactions.

4. Allowing the payee to construct their half of the transaction and send it to the payer where they can finish constructing the transaction before publishing it to the blockchain.

[Cestrada]

1. In addition to timelock, Beam adds the ability to also specify the upper time limit after which the transaction can no longer be included in a block.
2. Beam encourages users to recycle transaction kernels by using a fee refund model.
3. Beam allows both parties to be asynchronous by using a Secure Bullet in Board system that is run on Beam full nodes.
4. Beam plans to support one sided transactions by kernel fusion where 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.

[Uyan]

1. Grin uses a timelock, “which prevents a transaction from being added to a block before a certain time”. Beam has the additional functionality of an upper time limit to this timelock, “after which the transaction can no longer be included in a block”.

2. Beam proposes recycled transaction kernels to improve scalability. They encourage users to partake in this feature through a fee refund model.

3. With Grin, both parties need to be online simultaneously.
   With Beam, using a Secure Bulletin Board System ( SBBS ), parties can be online asynchronously and still complete transactions.

4. Beam also plans to support one-sided transactions:

“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. The payer can then finish constructing the transaction and publish it to the blockchain.”

This will be implemented using kernel fusion:

“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”

[Bull75rm]

1. BEAM includes the ability to also specify an upper time limit.
2. BEAM includes a fee refund model for these types of transactions.
3. BEAM has implemented a Secure Bulletin Board System (SBBS) that is run on BEAM full-nodes to allow for asynchronous negotiation of transactions.
4. With a process called kernel fusion, whereby a kernel can include a reference to another kernel, so that it is only valid when both a presented in s transaction.

[LukeS]

1. Allows the user to specify an upper time limit, after which the transaction can no longer be included in a block.
2. If you use this they will include a fee refund model.
3. They have implemented a Secure Bulletin Board System that is run on BEAM full-nodes to run this.
4. By using a process called kernel fusion.

[mervxxgotti]

• GRIN uses a timelock. What additional functionality does BEAM add to this timelock? — specify upper limit on time lock, which specifies a time in which transaction can no longer be included in block
• BEAM proposes to improve scalability by letting users recycle transaction kernels. How will they encourage users to use this feature? — through a fee refund model
• In a GRIN transaction, both parties must be online at the same time. How does BEAM allow this to be done asynchronously? — through SBBS on BEAM full nodes
• How does BEAM plan to support one-sided transactions? — using kernel fusion where kernel can reference other kernel and this only works when both kernels are present

[ol_frank]

• GRIN uses a timelock. What additional functionality does BEAM add to this timelock?
  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, 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 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?
  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.

[vegas316]

1. GRIN uses a timelock. What additional functionality does BEAM add to this timelock?
BEAM supports setting an explicit incubation period on a UTXO, which limits its ability to be spent to a specific number of blocks after its creation.
2. BEAM proposes to improve scalability by letting users recycle transaction kernels. How will they encourage users to use this feature?
By implementing a fee rebate model.
3. In a GRIN transaction, both parties must be online at the same time. How does BEAM allow this to be done asynchronously?
Using a Secure Bulletin Board System running on full BEAM nodes.
4. How does BEAM plan to support one-sided transactions?
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.

[Zulu1]

• GRIN uses a timelock. What additional functionality does BEAM add to this timelock? The ability to specify an upper time limit to which a transaction can be added to the block. If a transaction is not included on the main block after a certain time, it will not appear.

• BEAM proposes to improve scalability by letting users recycle transaction kernels. How will they encourage users to use this feature? Beam encourage users by including a fee refund model.

• In a GRIN transaction, both parties must be online at the same time. How does BEAM allow this to be done asynchronously? BEAM 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 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.

[Samuel1]

1. The additional functionality is an upper time limit of the timelock.
   2.Scalability will be increased via a fee refund model based on a recycling process.
   3.BEAM allows transaction to be asynchronous via implementation of the SSBS(Secure Bulletin Board System).
   4.One-sided transaction are supported via “kernel fusion”, where a kernel can be a reference of another kernel.

[Aiisnotbad]

@Grant_Hawkins

• GRIN uses a timelock. What additional functionality does BEAM add to this timelock?
• BEAM proposes to improve scalability by letting users recycle transaction kernels. How will they encourage users to use this feature?
• In a GRIN transaction, both parties must be online at the same time. How does BEAM allow this to be done asynchronously?
• How does BEAM plan to support one-sided transactions?

. An upper block number limit.

. Through a fee refund scheme.

. By using Secure Bulletin Board System, which basically uses master nodes as proxies/buffers for transactions being built by two parties.

. By using the « kernel fusion » where a user will be able to predefine his part of a transaction he is expecting to receive.

[HemalT]

1. GRIN uses a timelock. What additional functionality does BEAM add to this timelock?
   BEAM also supports the traditional timelock feature, but includes the ability to also 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, it will never appear.
2. BEAM proposes to improve scalability by letting users recycle transaction kernels. How will they encourage users to use this feature?
   BEAM includes a fee refund model for these types of transactions. This feature will not be part of the initial release.
3. 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) which is run on BEAM full nodes to allow for asynchronous negotiation of transactions.
4. How does BEAM plan to support one-sided transactions?
   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.

[maxs]

1. GRIN uses a timelock. What additional functionality does BEAM add to this timelock?
   Beam also “includes the ability to also specify an upper time limit, after which the transaction can no longer be included in a block”.

2. BEAM proposes to improve scalability by letting users recycle transaction kernels. How will they encourage users to use this feature?
   With a fee refund model for this type of transactions.

3. 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”

4. How does BEAM plan to support one-sided transactions?
   “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. The payer can then finish constructing the transaction and publish it to the blockchain.” This is enabled by a process called Kernel Fusion.

[walter_w]

1. the upper time limit 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, it will never appear
2. by using a refund model for this type of transaction
3. by using a secure bulletin board system
4. by allowing the transaction to be created in multiple steps by each person

[Denzel]

1.- An incubation period, which instead of broadcasting the transaction in later blocks, it directly does not let you spend the outputs until a certain period of time.

2.- By implementing a fee refung model.

3.- With the implementation of SBBS, which is run on full-nodes.

4.- With kernel fusion, a kernel references another kernel so the tx is only valid if both are present.

[Fjell]

1. GRIN uses a timelock which prevents a transaction from being added to a block before a certain time. BEAM also supports this traditional timelock feature like GRIN, but additionally includes the ability to also 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, it will never appear.
2. BEAM proposes to improve scalability by letting users recycle transaction kernels. In order to incentivize transactions to be built in this way, BEAM includes a fee refund model for these types of transactions. This feature will not be part of the initial release however.
3. In a GRIN transaction, both parties must be online at the same time connecting directly to one another using a socket-based channel for a “real-time” session. In contrast, BEAM plans to allow this to be done asynchronously via implementation of a Secure Bulletin Board System (SBBS) that is run on BEAM full-nodes to allow for asynchronous negotiation of transactions.
4. BEAM 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. Under the normal Mimblewimble system this is not possible, because it would involve revealing your blinding factor to the counterparty. 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.

[Meddodreddo]

• GRIN uses a timelock. What additional functionality does BEAM add to this timelock?
  Customizable time lock. It’s also got something else, let’s call it “block lock”, where it limits the number of blocks to which the transaction can be added.

• BEAM proposes to improve scalability by letting users recycle transaction kernels. How will they encourage users to use this feature?
  By having the “owner” add a multiplier to old kernels.

• In a GRIN transaction, both parties must be online at the same time. How does BEAM allow this to be done asynchronously?
  A secure bulletin board system run on nodes

• How does BEAM plan to support one-sided transactions?
  By having the receiver construct their half of the transaction then posting it to the sender for completion. This would involve referencing another kernel (kernel fusion) so as not to reveal the receivers blinding factors to the sender.

[tony1999]

1. BEAM enables the specification of an upper time limit on the timelock, which fixes a time after which the transaction will no longer be included in the blockchain. This means that if a user on the receiving end has not received the transaction after a set period of time, they can be sure it will never appear.
2. BEAM includes a fee refund model for these types of transactions that reuse the old kernel.
3. BEAM has implemented an SBBS system that is run on full-nodes. This allows full asynchronous negotiation of transactions.
4. Using kernel fusion (not possible in the original MW protocol), where the payee can build their half of the transaction and send it to the payer.