Pablo Greco

179 posts

Pablo Greco

Pablo Greco

@PabloSGreco

a hobbyist and hacker who is a real threat to open source companies everywhere

Katılım Haziran 2016
124 Takip Edilen382 Takipçiler
Pablo Greco
Pablo Greco@PabloSGreco·
@evanwinget @Liquid_BTC Yes, it does need 100% to activate, but no, no concerns about functionaries not updating, it's just a matter of operators getting to it
English
1
0
6
92
Evan Winget ⚡
Evan Winget ⚡@evanwinget·
@Liquid_BTC It needs 100% of functionaries to signal support to activate as currently specified, right? Any concerns with one or more of the remaining 6 functionaries failing to signal?
English
2
1
5
490
Liquid Network 🌊
Liquid Network 🌊@Liquid_BTC·
Simplicity update: There are now ten functionary operators signaling for the deployment of the much-anticipated smart contracting language, which brings easier developer UX and expressivity to Bitcoin L2. What are you most excited to start building? simplicity-lang.org
Liquid Network 🌊@Liquid_BTC

There are now three Liquid functionary operators signaling for Simplicity. Activation requires unanimous support from all functionaries over a window of 10,080 blocks. Keep an eye on the Simplicity tracker 👇 and follow as it unfolds in real-time! simplicity-lang.org

English
7
17
73
56.6K
Anthony Towns
Anthony Towns@ajtowns·
Seems pretty weird that @blksresearch's simplicity is potentially activating on Liquid mainnet any week now, but there hasn't been a tweet or blog post about it, or a taproot-watch-like site setup. github.com/ElementsProjec…
English
6
4
42
3.4K
Pablo Greco
Pablo Greco@PabloSGreco·
@ajtowns @blksresearch The version that contains that commit is still in RC, so none of the functionaries have it installed. That version is being tested internally. Once we're comfortable with it, we'll create a release version and the functionary operators will start signaling support.
English
1
1
4
80
Pablo Greco
Pablo Greco@PabloSGreco·
@stonychambers @Liquid_BTC Because that's the baseline that was chosen, anything lower than that would make it too easy (cheap) to spam the network. Also I don't think liquid adoption (or lack thereof) is related to fees
English
0
0
2
26
Bitcoin Asset Research
Bitcoin Asset Research@stonychambers·
@Liquid_BTC Why are fees lower bounded at 0.1 sats per vbyte on Liquid when the blocks rarely have more than a few transactions in them? Making the minimum fee 0 will allow for a better fee market to develop.
English
1
0
1
38
Liquid Network 🌊
Liquid Network 🌊@Liquid_BTC·
Indeed, and this is why the Liquid Network deploys the same UTXO model and underlying primitives as Bitcoin. In addition to greater security, the self-contained verifiability of a UTXO transaction also boosts chain reliability, scalability, and user privacy. To truly create 'the future of finance,' institutions and industry leaders must select the right architecture, and we believe Bitcoin and its second-layer protocols offer that solution. 🌊⚡️
Alexander Leishman 🇺🇸@Leishman

It absolutely has something to do with Ethereum: in Bitcoin (a UTXO chain) you are signing off on the state transition from a transaction, which is very easily verified in a hardware wallet screen. In Ethereum you are signing off on fund movement AND a command to send a smart contract (which could lead to further fund movement) – a VERY error prone UX. ETH transactions don't represent the state transition, they represent the command triggering the state transition.

English
3
17
105
20.6K
Pablo Greco
Pablo Greco@PabloSGreco·
@Brendonicus @Liquid_BTC In theory, yes, the same logic still applies because it is also a UTXO based chain, but there are certain caveats: 1) Blocks are not that full, so base feerate is still used. 2) Base feerate is 1/10 of bitcoin (0.1 sat/vByte)
English
0
1
6
501
Brendonicus
Brendonicus@Brendonicus·
@Liquid_BTC Do users have to actively manage UTXO sizes on Liquid the same way they have to on the base chain to avoid small, potentially future unspendable UTXOs?
English
1
0
3
204
calle
calle@callebtc·
By now I would've thought that Lightning with a self-hosted remote signer would be a thing.
English
6
1
18
2.2K
Pablo Greco
Pablo Greco@PabloSGreco·
@callebtc @byronhambly @_pretyflaco @tierotiero You don't need any emulator, the code published there has all the code to sign everything if you provide the plaintext keys. It's obviously not prod ready, but the network in my demo is fully functional
English
1
0
3
56
Matt Ahlborg
Matt Ahlborg@MattAhlborg·
@BtcpayServer, @Liquid_BTC, @LunaNode I've got kind of an unusual setup here, with LBTC, LTC, and DOGE nodes, but no BTC node. LBTC seems to not want to do IBD. Does it need a BTC node to function properly?
Matt Ahlborg tweet media
English
1
0
0
157
Pablo Greco
Pablo Greco@PabloSGreco·
@MattAhlborg @prochronist @BtcpayServer @Liquid_BTC @LunaNode Elements by default checks the validity of the pegins against bitcoin, and that's why it's failing to start without it. If you don't want to validate the peg-ins, you can add `validatepegin=0` to your elements.conf and it will work without bitcoin
English
1
0
2
59
Matt Ahlborg
Matt Ahlborg@MattAhlborg·
@prochronist @BtcpayServer @Liquid_BTC @LunaNode A little confused by what you said... you said "or". Can you explain what `validatepegins=0` is? Does it make it so that I might not need the BTC node? Or I'll need the BTC node no matter what?
English
1
0
0
36
Pablo Greco
Pablo Greco@PabloSGreco·
@alexiarsteinn Recuerdo esa charla, muy bien esos warnings! Yo lo que uso mucho es pisar el pushurl en git, para siempre subir a mi fork y nunca al repo posta. `pushurl = you really didn't want to do that`
Español
1
0
2
120
Lexi @alexia@floss.social
Lexi @[email protected]@alexiarsteinn·
quemando la iso a un usb me sale este msg y pense WTF, y luego recorde que lo habia hecho en joda hace unos meses atras durante una charla en discord. Que opa. Jaja.
Lexi @alexia@floss.social tweet media
Español
3
2
50
2.2K
Pablo Greco
Pablo Greco@PabloSGreco·
@Ctrlbreak @Excellion @Mr21Million @GaryLeland @AquaBitcoin Who is the Technical provider of the Liquid federation? Blockstream. Who controls the wallet that receives the funds from the fees? Blockstream, on behalf of the federation, as part of its duty as the technical provider. Who owns said fees? The Liquid Federation.
English
0
0
1
49
Pablo Greco
Pablo Greco@PabloSGreco·
@TO @brian_trollz @bergealex4 @Liquid_BTC The normal spending path is the 11/15 signature from the functionaries. The emergency keys are only usable if the utxo is more than 4032 blocks old, so they are refreshed constantly to avoid that.
English
0
0
4
27
Alex B 👾
Alex B 👾@bergealex4·
For what it's worth @Liquid_BTC is probably the most secure and censorship-resistant "layer 2" in production across the entire industry. That it's basically a ghost town shows how much people actually care about either of those things.
English
13
5
94
9K
Pablo Greco
Pablo Greco@PabloSGreco·
@nikzh @3xplcom Using a tool like hal, you can do hal address create --script <hex> and it will show you 2 of the addresses. The third one was a variation of the first fedpegscript but with 2016 instead of 4032 blocks (replacing c00b with e007)
English
0
0
1
46
Pablo Greco
Pablo Greco@PabloSGreco·
@nikzh @3xplcom Those are the 3 addresses used in the history of liquid and you can validate them looking at the fedpegscript field in each header divisible by 20160 (epoch length) after the dynafed activation in block 1517040
English
1
0
0
62
Pablo Greco
Pablo Greco@PabloSGreco·
@alexiarsteinn Mi regla dice que si escribo "declare -A" en bash, es el momento de pasar a python porque todo está a punto de descarrilar.... 🤣
Español
1
0
1
29
Lexi @alexia@floss.social
Lexi @[email protected]@alexiarsteinn·
Este array asociativo tambien no me termina de convencer pero fue lo mejor que se me ocurrio para traducir lo que me choreo via webscraping jaja
Lexi @alexia@floss.social tweet media
Español
1
0
2
651