You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi friends, I've read through the Hop protocol white paper and the contracts. Amazing work!
I've had some minor and general questions regarding the details of Hop protocol. I can not find other ways to get in touch so I just post them here. Let me know if I should post them somewhere.
the two links in Diagram section in readme do not seem to be the correct ones
don't know if it's just me, but the transferFromBridge/transferToBridge functions create a small confusion for me:
transferFromBridge actually transfer "to" some address while transferToBridge actually transfer "from" some address
swapAndSend function mentioned in readme seems to reside in L2_AmmWrapper contract instead of L2_bridge.
Are they refering to the same contract?
4-1. I see that L2_Bridge inherit Bridge contract so it will also have bondWithdrawal function. I think it's possible that a bonder accidentally call bondWithdrawal on L2_bridge contract? (though not really a big deal)
4-2. these two functions seem to differ only in whether they have AMM swap functionality or not?
Wait for the sending layer-2 to be confirmed on layer-1 (approximately 7 days)
User or Relayer calls L2_Bridge.withdraw() on the receiving layer-2
are there any more steps or wait time between these last two steps?
if I understand correctly, even if sending layer-2 is confirmed on layer-1, it doesn't mean the state on receiving layer-2 is updated immediately?
Can you explain more on this part in the Expected usage section in readme?
"Credit is added to the Bonder's credit account each time transactions (from/to any chain) are successfully confirmed on layer-1. Debit is added to the Bonder's debit account each time transactions are sent (from/to any chain) but not yet confirmed on layer-1."
6-1. what kind of transactions are to be confirmed? transfer? withdraw? bondWithdraw?
6-2. what would be the circumstances where transactions are sent but not yet confirmed on layer-1?
(it would be helpful to better understand what type of transactions and in what circumstances would have an affect on both credit and debt)
if there's transferId for each transfer, it seems it should be able to prevent multiple bonder bonding for same transfer at the same time?
do you have guidelines for how to become a bonder? it would be really helpful for us to better understand the protocol and assessing the risk!
Thanks alot!
The text was updated successfully, but these errors were encountered:
Hi friends, I've read through the Hop protocol white paper and the contracts. Amazing work!
I've had some minor and general questions regarding the details of Hop protocol. I can not find other ways to get in touch so I just post them here. Let me know if I should post them somewhere.
the two links in Diagram section in readme do not seem to be the correct ones
don't know if it's just me, but the
transferFromBridge
/transferToBridge
functions create a small confusion for me:transferFromBridge
actually transfer "to" some address whiletransferToBridge
actually transfer "from" some addresscontracts/contracts/bridges/L1_ERC20_Bridge.sol
Lines 25 to 31 in d47c0eb
swapAndSend
function mentioned in readme seems to reside inL2_AmmWrapper
contract instead ofL2_bridge
.Are they refering to the same contract?
4-1. I see that
L2_Bridge
inheritBridge
contract so it will also havebondWithdrawal
function. I think it's possible that a bonder accidentally callbondWithdrawal
onL2_bridge
contract? (though not really a big deal)4-2. these two functions seem to differ only in whether they have AMM swap functionality or not?
are there any more steps or wait time between these last two steps?
if I understand correctly, even if sending layer-2 is confirmed on layer-1, it doesn't mean the state on receiving layer-2 is updated immediately?
Can you explain more on this part in the Expected usage section in readme?
"Credit is added to the Bonder's credit account each time transactions (from/to any chain) are successfully confirmed on layer-1. Debit is added to the Bonder's debit account each time transactions are sent (from/to any chain) but not yet confirmed on layer-1."
6-1. what kind of transactions are to be confirmed? transfer? withdraw? bondWithdraw?
6-2. what would be the circumstances where transactions are sent but not yet confirmed on layer-1?
(it would be helpful to better understand what type of transactions and in what circumstances would have an affect on both credit and debt)
if there's transferId for each transfer, it seems it should be able to prevent multiple bonder bonding for same transfer at the same time?
do you have guidelines for how to become a bonder? it would be really helpful for us to better understand the protocol and assessing the risk!
Thanks alot!
The text was updated successfully, but these errors were encountered: