Nickolas Goline

213 posts

Nickolas Goline

Nickolas Goline

@ngoline

Working on NLightning, a dotNet implementation of the Lightning Network

World Katılım Haziran 2009
144 Takip Edilen284 Takipçiler
Nickolas Goline
Nickolas Goline@ngoline·
@AirbnbHelp Update: Case closed! A huge thanks to Supervisor Bruna and @AirbnbHelp for fixing the administrative error. We reached a fair agreement, and a coupon was provided to successfully rebook our family trip. Crisis averted! Thank you for saving our holiday. 🇵🇹✈️
English
1
0
0
21
Nickolas Goline
Nickolas Goline@ngoline·
@AirbnbHelp Update: Support promised a Supervisor contact within 3 hours regarding my wrongful cancellation caused by agent error. My family travels in 6 days. I expect Airbnb to cover the difference for a new booking via AirCover. Clock is ticking.
English
3
0
1
34
Nickolas Goline
Nickolas Goline@ngoline·
@AirbnbHelp Your support agent instructed me to fix a payment error via bank dispute and PROMISED my reservation wouldn't be cancelled. It just was. I travel in 6 days with a child. Help immediately!
English
6
0
0
39
Nickolas Goline
Nickolas Goline@ngoline·
Couldn't be more happy! An acquaintance asked Google 'how to decode a #BOLT11 invoice in C#' and Gemini told them to use #NLightning! Slowly but surely we're getting somewhere...
Nickolas Goline tweet media
English
0
0
6
90
Satsconf
Satsconf@satsconf_·
Durante os dois dias de Satsconf, foram mais de 3 mil pagamentos processados e quase 19 milhões de sats movimentados. Um retrato do poder do Bitcoin em tempo real. 🤘 A operação contou com a infraestrutura da @Bitcoinize e @BtcpayServer , e o apoio técnico de @ngoline , @jaoNoctus e Felipe Vallades, que garantiram o funcionamento impecável de todos os pagamentos.
Satsconf tweet media
Português
1
5
29
3.8K
Nickolas Goline
Nickolas Goline@ngoline·
É sempre um prazer fazer parte de um evento tão incrível. Ver mais de 1100 pessoas usando #Bitcoin como se deve, muitas pela primeira vez, é mágico. Realmente tinha que sair perfeito depois de 3 anos polindo o processo. ♥️ @jaoNoctus, @vallades e @lucasdcf
Satsconf@satsconf_

Durante os dois dias de Satsconf, foram mais de 3 mil pagamentos processados e quase 19 milhões de sats movimentados. Um retrato do poder do Bitcoin em tempo real. 🤘 A operação contou com a infraestrutura da @Bitcoinize e @BtcpayServer , e o apoio técnico de @ngoline , @jaoNoctus e Felipe Vallades, que garantiram o funcionamento impecável de todos os pagamentos.

Português
1
0
10
260
Nickolas Goline
Nickolas Goline@ngoline·
@farleir @lorenzolfm Essa foto foi tirada quando chegou a caixa na casa há vários meses, parecia Natal e eu só queria abrir pra ver a beleza interna da máquina. Além disso tenho uns 16 anos de experiência com hardware e não somos inconsequentes de ligar 2 fontes de 800W cada sem nos preparar...
Português
0
0
1
20
Nickolas Goline
Nickolas Goline@ngoline·
@farleir @lorenzolfm Na foto da pra ver que não ligamos o servidor DELL naquela tomada, que estava solta pra avaliar a instalação do local. Ele não foi ligado até chegar o rack e ajeitarmos a fiação do outro andar, além de subir as conexões de fibra, switch, etc...
Português
1
0
0
20
Lorenzo
Lorenzo@lorenzolfm·
Ta acontecendo um movimento em SP muito massa de hacker house Um lugar onde a galera que trabalha com freedom tech e open source se junta e são livres para ficar o dia todo construindo É a Disney de quem está construindo um mundo mais livre O nome é Casa 21
Lorenzo tweet mediaLorenzo tweet media
Português
21
43
761
32.6K
Nickolas Goline
Nickolas Goline@ngoline·
@Zerocodename1 @lifofifo As far as I understand it, to publish the tx both parties have to add their inputs and sign it. This uses PSBTs and one party have to create the contract with both parties input info, then it's only valid if it has the 2 signatures needed for the 2 pre-agreed inputs.
English
0
0
1
19
lifofifo ◉
lifofifo ◉@lifofifo·
Here's a different approach to BIP-444 futures using pre-signed transactions and larger OP_RETURN (300 bytes) for settlement, the most contentious aspect of this debate. github.com/lifofifoX/bip4… This should work well with PSBT.io + Xverse/Unisat. Shoutout to @Rob1Ham for pushing the futures concept. Highly recommend reading the pinned post on Rob's profile to understand why this matters. NFA/DYOR
Rob Hamilton@Rob1Ham

I have now fully open sourced the code which creates this on-chain BIP-444 futures contract! The contract starts with an atomic deposit into the contract address of 1 BTC each (to make sure both parties put in the same amount into the contract address). Context: BIP-444 makes the use of OP_IF & OP_NOTIF consensus INVALID upon activation. The contract is built as follows: The taproot address uses the NUMS point as described in BIP341, to provably show the key path is not active. We have two parties, a "YES" (444 activates) and "NO" (444 does NOT activate). YES and NO for short. The first leaf is a 2 of 2 multisig of both parties. This exists to be able to self send the UTXO AFTER BIP 444 activates. This is because BIP-444 just added a clause that UTXOs created before activation will NOT have the BIP-444 consensus rules applied to them. This self send removes that exception. The second leaf: has 2 ways you can spend with it, a 2 of 2 (YES and NO) multisig, just like the first leaf OR the NO party, with a time lock which is LESS THAN the third tap leaf. This is important because it uses OP_NOTIF The Third Leaf: The YES party can spend, after a time lock AFTER the second leaf. The order of the timelocks is important. If BIP-444 activates, the spending condition that can spend before you will be consensus invalid, so it doesn't matter if you believe 444 activates. So to summarize: - If BIP-444 DOES activate, the party who believes it will be able to use the second tap leaf to get 2 BTC out. - If BIP-444 DOES NOT activate, the party who believes that will use the third tap leaf to get 2 BTC out. Since each side is highly confident in their position, the fair market price is a 1:1 ratio, implying 50% likelihood. With 85 days until activation, this contract as written gives you an implied ~430% APY on your bitcoin! The risk is being incorrect on your opinion of BIP-444 activating. You could modify the collateral each side puts up to get different implied odds of the futures contract as well. Code and example address below 👇

English
8
8
79
20.1K
Nickolas Goline retweetledi
Rob Hamilton
Rob Hamilton@Rob1Ham·
I have now fully open sourced the code which creates this on-chain BIP-444 futures contract! The contract starts with an atomic deposit into the contract address of 1 BTC each (to make sure both parties put in the same amount into the contract address). Context: BIP-444 makes the use of OP_IF & OP_NOTIF consensus INVALID upon activation. The contract is built as follows: The taproot address uses the NUMS point as described in BIP341, to provably show the key path is not active. We have two parties, a "YES" (444 activates) and "NO" (444 does NOT activate). YES and NO for short. The first leaf is a 2 of 2 multisig of both parties. This exists to be able to self send the UTXO AFTER BIP 444 activates. This is because BIP-444 just added a clause that UTXOs created before activation will NOT have the BIP-444 consensus rules applied to them. This self send removes that exception. The second leaf: has 2 ways you can spend with it, a 2 of 2 (YES and NO) multisig, just like the first leaf OR the NO party, with a time lock which is LESS THAN the third tap leaf. This is important because it uses OP_NOTIF The Third Leaf: The YES party can spend, after a time lock AFTER the second leaf. The order of the timelocks is important. If BIP-444 activates, the spending condition that can spend before you will be consensus invalid, so it doesn't matter if you believe 444 activates. So to summarize: - If BIP-444 DOES activate, the party who believes it will be able to use the second tap leaf to get 2 BTC out. - If BIP-444 DOES NOT activate, the party who believes that will use the third tap leaf to get 2 BTC out. Since each side is highly confident in their position, the fair market price is a 1:1 ratio, implying 50% likelihood. With 85 days until activation, this contract as written gives you an implied ~430% APY on your bitcoin! The risk is being incorrect on your opinion of BIP-444 activating. You could modify the collateral each side puts up to get different implied odds of the futures contract as well. Code and example address below 👇
Rob Hamilton tweet mediaRob Hamilton tweet mediaRob Hamilton tweet media
Rob Hamilton@Rob1Ham

For anyone who thinks BIP 444 will activate, I will happily offer you an ability to make more bitcoin. We each deposit 1 BTC into a taproot address with two spending conditions: 1. Time locked so that you can withdraw June 1st next year at a depth of 1 in the tap tree. 2. Time locked so I can withdraw May 1st next year at a depth of 128 in the tap tree. If BIP444 activates, you get 2 BTC out of the address (because my spend path would be consensus invalid). If BIP444 does not activate, I get 2BTC out of the address. DMs are open, we can use a dedicated escrow agent as third key if necessary, would obviously provide auditable code to show there are no tricks. We can also atomically fund the transaction using a multi input transaction into this taproot address to guarantee all parties fund the address. Only condition is the bet is public. Willing to consider odds if you're of lower conviction.

English
49
45
267
198K
Nickolas Goline retweetledi
Michael Tidwell
Michael Tidwell@miketwenty1·
The amount of work @lucasdcf and his team put in to @satsconf_ is truly amazing this year. Loving the headphone setup in the noisy ballroom to make ultimate usage of the space with additional stages. Also shout-out to @jaoNoctus @ngoline for the behind the scenes support!
Michael Tidwell tweet media
English
2
14
77
10.4K
Nickolas Goline retweetledi
jaonoctus
jaonoctus@jaoNoctus·
Quer saber como conseguimos resolver o enigma da @tabconf pelo segundo ano consecutivo? Venha para o @satsconf_ conhecer os maiores e melhores cypherpunks brazucas 🇧🇷 @narcelio e @ngoline que me ajudaram nessa Links na thread 🧵👇
jaonoctus tweet media
Português
4
9
69
3.9K
Michael Tidwell
Michael Tidwell@miketwenty1·
Most people don't seem to know what "preimage" means. This will be a critical part of the CTB (Capture the Bitcoin) puzzle this year at @tabconf. It's very important to understand and use the same language when talking about tech. Don't arbitrarily hold yourself back from learning basic concepts that will help you discuss/debate and understand how things really work. Come to tab7 and level up.
English
7
6
46
4.8K
Nickolas Goline
Nickolas Goline@ngoline·
@btcinsider__ Actually we are already at the 75% mark. I'm planning for full compatibility by the end of 2026.
English
1
0
0
7
Nickolas Goline retweetledi
Vinteum
Vinteum@Vinteum_org·
On August 10, Vinteum turned 3 years old 🎉 To celebrate, we put together a 50-page report (available in English and Portuguese) covering everything we have accomplished so far, from developer contributions to education and community building in Brazil’s Bitcoin ecosystem 🧵👇
Vinteum tweet media
English
17
92
179
41.2K