Just made public LiquiDEX, a 2-steps non-interactive protocol to trade assets on the @Liquid_BTC blockchain. Based on long research made in the last 2 evenings by @LeoComandini and me.
github.com/RCasatta/Liqui… For the first mainnet trade, what could be at least as memorable as the "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks"? The beer on the newspaper gives me the hint, let's buy @drunkoshi 's beer!

1/n) I received a free Cobo Vault Pro from @BitcoinLixin, It is a hardware wallet offline-signing capable. It seems he is listening from feedback from the community to improve his products and so the following is my feedback (I am not a hardware expert). As seen in the previous photo, Cobo Vault comes with a warranty sticker, that helps to identify supply chain attacks. I would like to see the same stickers on the battery box since power analysis attacks are possible through a compromised power source.

After latest merge in @opentimestamps calendar server donations through lightning ⚡ with convenient qr codes are supported! Have a look at calendar Finney finney.calendar.eternitywall.com Calendar Finney is serving from 21 April 2017, more than 20M commitments in the bitcoin blockchain, could be more since all requests coming in the same second are grouped github.com/opentimestamps…

I went down the rabbit hole, 120 ms to sign and as many to verify was too much.
I knew libsecp256k1 was efficient (and, more important, secure) but I wanted to learn how it was as many as a _thousand_ times faster

https://twitter.com/RCasatta/status/1016032457924235264

The journey in the hole brought me to learn and implement:
* Jacobian coordinates
* Pre-caching G multiples
* Specific code for doubling points and mixed add
* Borrowing instead of copying
* Multiplying instead of powering for 2 or 3
* Avoiding any inverse in verify

1/ Yeah! @opentimestamps calendar Finney is now serving requests through Foxglove! A NSA-level codename for a super-fast requests aggregator, serving an high throughput of stamp requests! How does it work? github.com/opentimestamps… 2/ Foxglove works by aggregating the stamp requests received in a specified time frame, 100 ms at the moment. At the end of the time slice, a merkle tree is built, the tip is sent to the calendar, when the calendar replies all the pending requests are served.

1/ Yeah! Online incremental backup just got merged into @opentimestamps server github.com/opentimestamps… When next release will be deployed all the calendars server data could be live backupped by anyone! 2/ What does this mean? If you have an upgraded OpenTimestamps receipt you don't have to worry. If you have a Pending receipt you need some extra data to prove the commitment of your data in the blockchain. This data resides in the calendar servers.