The world’s first virtual Lightning Network conference and Hackaton is being organized on April 5-7 1019, anywhere in the world.
Winners of the hackathon will win the following prizes: 1st place = 0.3 BTC, 2nd = 0.2 BTC, 3rd = 0.1 BTC.
The Decentralized exchange BISQ recently rolled out a series of new upgrades including a twofold increase in trade limits for altcoins bringing the total trade limit to 2 BTC.
The release also fixes wallet and startup bugs and issues that were recently reported by users. The updates also include many improvements to Bisq DAO, a decentralized anonymous organiztion running over the testnet Bitcoin network.
It allows you to get paid in cryptocurrency just by sharing a simple URL using a new type of time-sensitive inoice page built into BTCPay.
BTCPay Server is an open-source cross platform, self-hosted bitcoin server compatible with Bitpay API.
What do you think about implementing Confidential Transactions in extension blocks? CT transactions go from extension block to extension block passing through normal blocks. It looks the perfect solution:
Soft fork: old nodes see CT transactions as “sendtoany” transactions
Safe: if there is a software bug in CT it’s impossible to create new coins because the coins move from normal block to normal block as public transactions
Legal: Exchanges can use public transactions so regulators can monitor their activity
Capacity increase: the CT signature is stored in the extension block, so CT transactions increase the maximum number of transactions per block
ZmnSCPxj agreed that capacity increase can boost network capacity for all full nodes, he thinks extension blocks are not real soft forks but rather “evil” soft forks as older nodes have to upgrade in order to function optimally, which makes extension blocks worse than soft forks.
The Bitcoin Developer Network (BDN) aims to become a community-driven project looking at educating the next wave of Bitcoin developers. This is a public invitation for developers, authors, editors, proofreaders, enthusiasts and technical writers to get in touch so that we may reduce the barrier to entry in developing solutions at various layers of this technology.
Considering it’s a community-driven initiative, it only seems fair to do this collaboratively.
Get in touch at firstname.lastname@example.org