PascalCoin is announcing version 6, a major protocol upgrade which puts Pascal at the forefront of next-generation cryptocurrency technology!
The PascalCoin community has come to consensus to implement the following game-changing protocol upgrades to PascalCoin:
PIP-0035 Block Policy: A simple and efficient layer-1 governance model which fundamentally innovates the “economic code” of crypto.
PIP-0041 Pay To Key: a solution to a fundamental problem in PascalCoin; how first-time users get their first account.
PIP-0027 E-PASA: a backwards compatible addressing scheme that enables an infinite address-space within PascalCoin.
PIP-0033: DATA operation RPC implementation: A description of the missing JSON-RPC methods related to DATA operations. …
Some time ago, I wrote an article promoting a mechanism to reward developers of cryptocurrencies alongside the miners.
Some time later, Craig Wright (who claims to be Satoshi Nakamoto, the inventor of Bitcoin) wrote a disparaging rebuke indirectly implying I’m a “techno-communist”.
Since his article doesn’t allow responses, I’ve responded to it here.
Nothing in Craig Wright’s article addresses the points made in my original article.
1. Craig claims Bitcoin 2010 was global adoption ready and didn’t need any more development yet NChain are clearly paying protocol developers to develop the BSV layer-1 client. It’s a total contradiction. If Bitcoin was global adoption ready in 2010, why do BSV insiders pay for protocol development? (Not referring to infrastructure or rolling back post-2010 updates). If Craig’s claims were true, they could simply revert the BSV codebase to 2010 with one git command and BSV should be global adoption ready. Instead they’re paying developers (likely into the $millions) out of their own pockets. …
Spans are special structs in .NET Core designed to provide pointer-like constructs in safe, managed contexts. This allows array and buffer manipulation similar to how how they’re done in C++, C and Pascal and with comparable performance.
byte byteArr = …;
// implicit cast
ReadOnlySpan<byte> span = byteArr;
Span<byte> span2 = byteArr;
- use ReadOnlySpan if you never need to change a value
- only use Span if you need to change a value
2. Spans encapsulate “offset and length” as a well as pointer. Thus method signatures like:
void SomeMethod(byte arr, int offset, int length)
I am writing this to publicly warn crypto-users about disturbing new behavior from Bittrex, one that’s oddly reminiscent of Mt Gox before they collapsed.
Bittrex have decided to freeze my 2-year long account despite relatively minor trading activity and being a fully-verified and KYC’d user.
Many in the crypto-sphere have heard of “transaction malleability” and that it’s “bad”. But, what is “transaction malleability” and why is it bad? Let’s dive into it quickly.
In a cryptocurrency such as Bitcoin, transactions are the atomic operations that transfer value between users. Users create transactions and publish them to the network. Those transactions propagate the network and are eventually mined into the blockchain. The blockchain is used by the recipients to determine if a transaction is confirmed or not.
Now, with millions of transactions flying around, how do users quickly identify them so as to be able to distinguish between them? How can a bunch of disconnected users across the globe quickly and uniquely identify transactions in the same way but without using some slow, global registry system? …
Miners own their hardware.
Why should developers have any say in what miners do with their hardware?
Likewise, developers own their repos.
Why should miners have any say in what developers do with their repos?
Cryptocurrency development is difficult. It requires a high degree of technical competence and 24/7 readiness in order to respond to any issue.
Mining cryptocurrency is expensive. It requires big investments and constant maintenance.
Both development and mining consume time, labour and material and both are necessary to maintain the cryptocurrency ecosystem.
When Satoshi launched Bitcoin, he added a mechanism to reward miners for their contribution. However, no such reward was added for developers. It was assumed development would be contributed for free on an altruistic basis. …