patrick [ARCHIVE] / is on Nostr

⚠️ This account is not associated with a real person. It's an archival account for mailing list messages.
🗓️ Active from 2014-04-19 to 2014-12-10
💬 Posted a total of 2 messages
📚 Participated in the following categories: Bitcoin-development
🔇 Please do not DM this user as it's used for archive purposes only.

Last Notes

2023-06-07 15:27:46

- reply

📅 Original date posted:2014-12-10
📝 Original message:The goal is to have an opportunity cost to breaking the rules.
Proof of Burn is a real cost for following the rules.
On 12/10/2014 01:35 AM, Tamas Blummer wrote:
> We spend scarce resources external to the digital realm to create Bitcoin. Real world sacrifice is needed to avoid “nothing at stake” and sybil attacks. With Bitcoin we now have a scarce resource within the digital realm, so it appeals my intuition to re-use it for sacrifice instead of linking again an external, real world resource.
>
> In following I outline a new mining algorithm for side chains, that burn Bitcoins to secure them.
>
> The side chain block validity rules would require that a transaction on the Bitcoin block chain provably destroys Bitcoins with an OP_RET output, that contains the hash of the block header of the side chain. To also introduce a lottery, the burn transaction’s hash is required to satisfy some function of the block hash it was included in on the Bitcoin block chain. For example modulo m of the burn transaction hash must match modulo m of the block hash, that is not known in advance.
>
> Those who want to mine the side chain will assemble side chain block candidates that comply the rules of the side chain, then a Bitcoin transaction burning to the hash of the block candidate and submit it to the Bitcoin network. Should he burn transaction be included into the Bitcoin block chain and the Bitcoin block’s hash satisfy the lottery criteria, then the block candidate can be submitted to extend the side chain.
>
> A side chain block header sequence would be accepted as side chain trunk if a sequence of Bitcoin SPV proofs for burn transactions prove, that linked blocks have the highest cumulative burn, if compared to alternative sequences.
>
> The Bitcoin miner will include burn transactions because they offer Bitcoin fees. Bitcoin miner can not selectively block side chains since the hashes associated with the burn do not disclose which side chain or other project they are for. Here you have a “merged mining” that does not need Bitcoin miner support or even consent.
>
> Mining difficulty of the side chain could be adjusted by stepping up the required burn and/or hardening the criteria that links a burn proof transaction with the bitcoin block hash it is included in.
>
> The difficulty to mine with burn would be dynamic and would also imply a floating exchange rate between Bitcoin and the side coin.
>
> Tamas Blummer
> Bits of Proof
>
> 00000000000000001172380e63346e3e915b52fcbae838ba958948ac9aa85edd
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20141210/ed5fdc7d/attachment.html>

2023-06-07 15:27:46

- reply

2023-06-07 15:18:52

- reply

📅 Original date posted:2014-04-19
📝 Original message:The alert system filters based on the clients version number.
The ubuntu bitcoin ppa is dynamically linked to openssl unlike the
binaries available from bitcoin.org
There is no way currently to notify users of 0.9.0 w/ static linking
without also notify 0.9.0 w/ dynamic linking.
On 04/19/2014 04:34 PM, Oliver Egginger wrote:
> Hello,
>
> bitcoin-qt produces on many systems an unnecessary alert:
>
> "URGENT: Upgrade required: see https://www.bitcoin.org/heartbleed"
>
> Especially the stable channel is affected:
>
> https://launchpad.net/~bitcoin/+archive/bitcoin
>
> This is a bit frightening for normal users. I think the best would be to
> turn off this message (if possible). It produces too many false
> positives and motivates people to maybe harmful workarounds.
>
> - oliver
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/NeoTech
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development