Bitcoin Forum
December 11, 2024, 08:49:15 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Is there a way to figure out a HTLC's time and date?  (Read 267 times)
BrutalBear (OP)
Newbie
*
Offline Offline

Activity: 11
Merit: 40


View Profile
July 21, 2022, 02:27:49 AM
Merited by hugeblack (4), NotATether (3), ABCbits (1)
 #1

Hi guys,

does anyone know the best way to figure out the time and date of a specific HTLC commitment transaction?
Zilon
Sr. Member
****
Offline Offline

Activity: 966
Merit: 421

Bitcoindata.science


View Profile WWW
July 21, 2022, 07:16:04 AM
Merited by hugeblack (4), pooya87 (3), ABCbits (3), NotATether (3), StanCrypt (3)
 #2

They are entirely done off-chain using multi-sig and scripting which allows for decentralized contracts. HTLC allows the two parties involved in the transaction  to update the balances in the channel instead of broadcasting on the blockchain making it impossible to figure out the time and date any HTLC commitment transaction was done since it wasn't hashed on the blockchain which means each commitment has two versions of the same output and each can only broadcast their own version of the transaction.

With the use of this nLockTime this transaction can remain open indefinitely and the final output locked via sequential number
BrutalBear (OP)
Newbie
*
Offline Offline

Activity: 11
Merit: 40


View Profile
July 21, 2022, 07:27:13 AM
 #3

They are entirely done off-chain using multi-sig and scripting which allows for decentralized contracts. HTLC allows the two parties involved in the transaction  to update the balances in the channel instead of broadcasting on the blockchain making it impossible to figure out the time and date any HTLC commitment transaction was done since it wasn't hashed on the blockchain which means each commitment has two versions of the same output and each can only broadcast their own version of the transaction.

With the use of this nLockTime this transaction can remain open indefinitely and the final output locked via sequential number


If I ask the two parties to provide these HTLCs to me, is there a way to figure out exact time/date?
Zilon
Sr. Member
****
Offline Offline

Activity: 966
Merit: 421

Bitcoindata.science


View Profile WWW
July 21, 2022, 07:43:45 AM
 #4

If I ask the two parties to provide these HTLCs to me, is there a way to figure out exact time/date?
In lightening network an escrow keeps a DB that tracks the recent channel-state and for this to be effective it comes with a timestamp so definitely if either of the parties decides to share the HTLCs to you then you can get the exact date and time of the transaction.
BrutalBear (OP)
Newbie
*
Offline Offline

Activity: 11
Merit: 40


View Profile
July 21, 2022, 02:53:24 PM
 #5

Thank you!
n0nce
Hero Member
*****
Offline Offline

Activity: 910
Merit: 5935


not your keys, not your coins!


View Profile WWW
July 21, 2022, 09:20:01 PM
Merited by hugeblack (4)
 #6

If I ask the two parties to provide these HTLCs to me, is there a way to figure out exact time/date?
In lightening network an escrow keeps a DB that tracks the recent channel-state and for this to be effective it comes with a timestamp so definitely if either of the parties decides to share the HTLCs to you then you can get the exact date and time of the transaction.
Wait what? If I open a Lightning channel with you, it's just between us, without any kind of escrow.
Or are you trying to say it would be possible to construct such an escrow? It's not 100% clear to me what you're trying to say.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
Zilon
Sr. Member
****
Offline Offline

Activity: 966
Merit: 421

Bitcoindata.science


View Profile WWW
July 22, 2022, 05:53:35 AM
 #7

Wait what? If I open a Lightning channel with you, it's just between us, without any kind of escrow.
Or are you trying to say it would be possible to construct such an escrow? It's not 100% clear to me what you're trying to say.
The escrow here reduces counter party risk. This is achieved by utilizing a cryptographic passphrase. In essence this time-based escrow  ensures the receiver of the payment acknowledges it with a given period of time and once this time elapses the receiver forfeits the payment. This receiver performs two tasks to access the fund.
  • Input the right passphrase
  • Then claim the payment
And this is done within a certain time frame in which if the receiver inputs an incorrect passphrase and cannot claim the payment within that time bound the receiver loses the payment
cygan
Legendary
*
Offline Offline

Activity: 3374
Merit: 9011


icarus-cards.eu


View Profile WWW
May 23, 2023, 09:33:33 AM
Merited by NotATether (1)
 #8

i would like to BTCump this topic up again, because there are now the following 5 slides, which explain this kind of payments (where hashlocks and timelocks are used) visually a little easier.
and i hope that it will be more understandable for one or the other user now Smiley


███████████▄
████████▄▄██
█████████▀█
███████████▄███████▄
█████▄█▄██████████████
████▄█▀▄░█████▄████████
████▄███░████████████▀
████░█████░█████▀▄▄▄▄▄
█████░█
██░█████████▀▀
░▄█▀
███░░▀▀▀██████
▀███████▄█▀▀▀██████▀
░░████▄▀░▀▀▀▀████▀
 

█████████████████████████
████████████▀░░░▀▀▀▀█████
█████████▀▀▀█▄░░░░░░░████
████▀▀░░░░░░░█▄░▄░░░▐████
████▌░░░░▄░░░▐████░░▐███
█████░░░▄██▄░░██▀░░░█████
█████▌░░▀██▀░░▐▌░░░▐█████
██████░░░░▀░░░░█░░░▐█████
██████▌░░░░░░░░▐█▄▄██████
███████▄░░▄▄▄████████████
█████████████████████████

█████████████████████████
████████▀▀░░░░░▀▀████████
██████░░▄██▄░▄██▄░░██████
█████░░████▀░▀████░░█████
████░░░░▀▀░░░░░▀▀░░░░████
████░░▄██░░░░░░░██▄░░████
████░░████░░░░░████░░████
█████░░▀▀░▄███▄░▀▀░░████
██████░░░░▀███▀░░░░██████
████████▄▄░░░░░▄▄████████
█████████████████████████
.
...SOL.....USDT...
...FAST PAYOUTS...
...BTC...
...TON...
BlackHatCoiner
Legendary
*
Offline Offline

Activity: 1736
Merit: 8448


Fiatheist


View Profile WWW
May 23, 2023, 05:39:22 PM
 #9

It may be just me right now, but isn't this sketch wrong? As far as I can see, Alice sends 1 BTC to Bob; she use Carol as an intermediary node to route her transaction to Bob. When Bob tells the secret to Carol, he doesn't need Alice to take the bitcoin. Alice has given him a transaction that grants Carol the bitcoin, given Carol has the preimage.

If Bob does not respond to Carol's preimage request, nothing happens. Carol cannot take the money, because he doesn't meet Alice's condition.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
cygan
Legendary
*
Offline Offline

Activity: 3374
Merit: 9011


icarus-cards.eu


View Profile WWW
May 24, 2023, 05:37:46 AM
 #10

It may be just me right now, but isn't this sketch wrong?
✂️

nope Wink
the channel in which the intermediary node participates must have the necessary liquidity to forward the payment. in this case, 1BTC should be available on Bob's side of the Alice<->Bob channel to ensure the successful routing of the tx. if Alice has a payment channel with Carol and wants to pay Bob, Carol acts as a node, charges a fee, and enables payment Smiley

███████████▄
████████▄▄██
█████████▀█
███████████▄███████▄
█████▄█▄██████████████
████▄█▀▄░█████▄████████
████▄███░████████████▀
████░█████░█████▀▄▄▄▄▄
█████░█
██░█████████▀▀
░▄█▀
███░░▀▀▀██████
▀███████▄█▀▀▀██████▀
░░████▄▀░▀▀▀▀████▀
 

█████████████████████████
████████████▀░░░▀▀▀▀█████
█████████▀▀▀█▄░░░░░░░████
████▀▀░░░░░░░█▄░▄░░░▐████
████▌░░░░▄░░░▐████░░▐███
█████░░░▄██▄░░██▀░░░█████
█████▌░░▀██▀░░▐▌░░░▐█████
██████░░░░▀░░░░█░░░▐█████
██████▌░░░░░░░░▐█▄▄██████
███████▄░░▄▄▄████████████
█████████████████████████

█████████████████████████
████████▀▀░░░░░▀▀████████
██████░░▄██▄░▄██▄░░██████
█████░░████▀░▀████░░█████
████░░░░▀▀░░░░░▀▀░░░░████
████░░▄██░░░░░░░██▄░░████
████░░████░░░░░████░░████
█████░░▀▀░▄███▄░▀▀░░████
██████░░░░▀███▀░░░░██████
████████▄▄░░░░░▄▄████████
█████████████████████████
.
...SOL.....USDT...
...FAST PAYOUTS...
...BTC...
...TON...
BlackHatCoiner
Legendary
*
Offline Offline

Activity: 1736
Merit: 8448


Fiatheist


View Profile WWW
May 24, 2023, 11:56:17 AM
 #11

if Alice has a payment channel with Carol and wants to pay Bob, Carol acts as a node, charges a fee, and enables payment
I don't disagree with Carol being an intermediary, and for the liquidity requirement. It just seems to me that even if Bob is unresponsive, Carol doesn't have anything to worry about. He will only transfer the bitcoin if Bob has given him the preimage. Otherwise, the condition in their script is not met. In the sketch, I see Carol asking Alice to give him his bitcoin back, but that payment has never happened. In fact, Carol never gives Alice bitcoin, he receives from Alice, and sends it to Bob.

(That, assuming Alice wants to send Bob a bitcoin, and the path looks like this: Alice <-> Carol <-> Bob)

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!