@Onff_line@AquaBitcoin@Brigithmgp@Liquid_BTC If you're running your own elements node (for liquid), you should be running at least version 23.3.1. If you're not running your node, it means nothing π
@cryptoquick@mononautical@OrangeSurfBTC@wiz Just for completeness, this is where the address is being added https://t.co/EeKTdwa2sP, at least for the static current workaround. And this is the address where everything is going https://t.co/XtehqtHGIN (new federation address)
@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
@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.
@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
@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)
@callebtc@byronhambly@_pretyflaco@tierotiero No, I destroyed it 5 minutes after the video, but you should be able to re-create it by watching the video. It was done fully from scratch
@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
@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
@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`
@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.
@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.
@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)
@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
@blurrCrystal@adam3us@mempool@Liquid_BTC Because that wallet pays for the sweeps and the peg-outs, so if there's no "extra", paying for fees would break the 1:1 peg.