Bitcoin Core version 0.15.1 released

04-12 21:21 - '[quote] Funny because their "codebase" was just a MYSQL database. Not sure there is much IP value to their "codebase". / In light of these current revelations, I'd like to remind Nick when he said [this] / [quote] ...' by /u/SometimesIwonderwhat removed from /r/Bitcoin within 11-16min

Left unacquired is the ChangeTip codebase
Funny because their "codebase" was just a MYSQL database. Not sure there is much IP value to their "codebase".
In light of these current revelations, I'd like to remind Nick when he said [this]1
"We have a privacy policy in big bold letters that says we will not sell user data without user permission, and we have no intention of ever doing so. It's fair for people to be paranoid, but there are no witches to be found here."
Hopefully they still have "no intention of ever doing so."
Context Link
Go1dfish undelete link
unreddit undelete link
Author: SometimesIwonderwhat
1: w**.co*ndesk.c*m/chan*etip-*eo-*ic*-sul*iv**-wo*t*sel*-us*r-d*ta/
Unknown links are censored to prevent spreading illicit content.
submitted by removalbot to removalbot [link] [comments]

Putting $400M of Bitcoin on your company balance sheet

Also posted on my blog as usual. Read it there if you can, there are footnotes and inlined plots.
A couple of months ago, MicroStrategy (MSTR) had a spare $400M of cash which it decided to shift to Bitcoin (BTC).
Today we'll discuss in excrutiating detail why this is not a good idea.
When a company has a pile of spare money it doesn't know what to do with, it'll normally do buybacks or start paying dividends. That gives the money back to the shareholders, and from an economic perspective the money can get better invested in other more promising companies. If you have a huge pile of of cash, you probably should be doing other things than leave it in a bank account to gather dust.
However, this statement from MicroStrategy CEO Michael Saylor exists to make it clear he's buying into BTC for all the wrong reasons:
“This is not a speculation, nor is it a hedge. This was a deliberate corporate strategy to adopt a bitcoin standard.”
Let's unpack it and jump into the economics Bitcoin:

Is Bitcoin money?

Or rather BTC doesn't act as money and there's no serious future path for BTC to become a form of money. Let's go back to basics. There are 3 main economic problems money solves:
1. Medium of Exchange. Before money we had to barter, which led to the double coincidence of wants problem. When everyone accepts the same money you can buy something from someone even if they don't like the stuff you own.
As a medium of exchange, BTC is not good. There are significant transaction fees and transaction waiting times built-in to BTC and these worsen the more popular BTC get.
You can test BTC's usefulness as a medium of exchange for yourself right now: try to order a pizza or to buy a random item with BTC. How many additional hurdles do you have to go through? How many fewer options do you have than if you used a regular currency? How much overhead (time, fees) is there?
2. Unit of Account. A unit of account is what you compare the value of objects against. We denominate BTC in terms of how many USD they're worth, so BTC is a unit of account presently. We can say it's because of lack of adoption, but really it's also because the market value of BTC is so volatile.
If I buy a $1000 table today or in 2017, it's roughly a $1000 table. We can't say that a 0.4BTC table was a 0.4BTC table in 2017. We'll expand on this in the next point:
3. Store of Value. When you create economic value, you don't want to be forced to use up the value you created right away.
For instance, if I fix your washing machine and you pay me in avocados, I'd be annoyed. I'd have to consume my payment before it becomes brown, squishy and disgusting. Avocado fruit is not good money because avocadoes loses value very fast.
On the other hand, well-run currencies like the USD, GBP, CAD, EUR, etc. all lose their value at a low and most importantly fairly predictible rate. Let's look at the chart of the USD against BTC
While the dollar loses value at a predictible rate, BTC is all over the place, which is bad.
One important use money is to write loan contracts. Loans are great. They let people spend now against their future potential earnings, so they can buy houses or start businesses without first saving up for a decade. Loans are good for the economy.
If you want to sign something that says "I owe you this much for that much time" then you need to be able to roughly predict the value of the debt in at the point in time where it's due.
Otherwise you'll have a hard time pricing the risk of the loan effectively. This means that you need to charge higher interests. The risk of making a loan in BTC needs to be priced into the interest of a BTC-denominated loan, which means much higher interest rates. High interests on loans are bad, because buying houses and starting businesses are good things.

BTC has a fixed supply, so these problems are built in

Some people think that going back to a standard where our money was denominated by a stock of gold (the Gold Standard) would solve economic problems. This is nonsense.
Having control over supply of your currency is a good thing, as long as it's well run.
See here
Remember that what is desirable is low variance in the value, not the value itself. When there are wild fluctuations in value, it's hard for money to do its job well.
Since the 1970s, the USD has been a fiat money with no intrinsic value. This means we control the supply of money.
Let's look at a classic poorly drawn econ101 graph
The market price for USD is where supply meets demand. The problem with a currency based on an item whose supply is fixed is that the price will necessarily fluctuate in response to changes in demand.
Imagine, if you will, that a pandemic strikes and that the demand for currency takes a sharp drop. The US imports less, people don't buy anything anymore, etc. If you can't print money, you get deflation, which is worsens everything. On the other hand, if you can make the money printers go brrrr you can stabilize the price
Having your currency be based on a fixed supply isn't just bad because in/deflation is hard to control.
It's also a national security risk...
The story of the guy who crashed gold prices in North Africa
In the 1200s, Mansa Munsa, the emperor of the Mali, was rich and a devout Muslim and wanted everyone to know it. So he embarked on a pilgrimage to make it rain all the way to Mecca.
He in fact made it rain so hard he increased the overall supply of gold and unintentionally crashed gold prices in Cairo by 20%, wreaking an economic havoc in North Africa that lasted a decade.
This story is fun, the larger point that having your inflation be at the mercy of foreign nations is an undesirable attribute in any currency. The US likes to call some countries currency manipulators, but this problem would be serious under a gold standard.

Currencies are based on trust

Since the USD is based on nothing except the US government's word, how can we trust USD not to be mismanaged?
The answer is that you can probably trust the fed until political stooges get put in place. Currently, the US's central bank managing the USD, the Federal Reserve (the Fed for friends & family), has administrative authority. The fed can say "no" to dumb requests from the president.
People who have no idea what the fed does like to chant "audit the fed", but the fed is already one of the best audited US federal entities. The transcripts of all their meetings are out in the open. As is their balance sheet, what they plan to do and why. If the US should audit anything it's the Department of Defense which operates without any accounting at all.
It's easy to see when a central bank will go rogue: it's when political yes-men are elected to the board.
For example, before printing themselves into hyperinflation, the Venezuelan president appointed a sociologist who publicly stated “Inflation does not exist in real life” and instead is a made up capitalist lie. Note what happened mere months after his gaining control over the Venezuelan currency
This is a key policy. One paper I really like, Sargent (1984) "The end of 4 big inflations" states:
The essential measures that ended hyperinflation in each of Germany,Austria, Hungary, and Poland were, first, the creation of an independentcentral bank that was legally committed to refuse the government'sdemand or additional unsecured credit and, second, a simultaneousalteration in the fiscal policy regime.
In english: *hyperinflation stops when the central bank can say "no" to the government."
The US Fed, like other well good central banks, is run by a bunch of nerds. When it prints money, even as aggressively as it has it does so for good reasons. You can see why they started printing on March 15th as the COVID lockdowns started:
The Federal Reserve is prepared to use its full range of tools to support the flow of credit to households and businesses and thereby promote its maximum employment and price stability goals.
In english: We're going to keep printing and lowering rates until jobs are back and inflation is under control. If we print until the sun is blotted out, we'll print in the shade.

BTC is not gold

Gold is a good asset for doomsday-preppers. If society crashes, gold will still have value.
How do we know that?
Gold has held value throughout multiple historic catastrophes over thousands of years. It had value before and after the Bronze Age Collapse, the Fall of the Western Roman Empire and Gengis Khan being Gengis Khan.
Even if you erased humanity and started over, the new humans would still find gold to be economically valuable. When Europeans d̶i̶s̶c̶o̶v̶e̶r̶e̶d̶ c̶o̶n̶q̶u̶e̶r̶e̶d̶ g̶e̶n̶o̶c̶i̶d̶e̶d̶ went to America, they found gold to be an important item over there too. This is about equivalent to finding humans on Alpha-Centauri and learning that they think gold is a good store of value as well.
Some people are puzzled at this: we don't even use gold for much! But it has great properties:
First, gold is hard to fake and impossible to manufacture. This makes it good to ascertain payment.
Second, gold doesnt react to oxygen, so it doesn't rust or tarnish. So it keeps value over time unlike most other materials.
Last, gold is pretty. This might sound frivolous, and you may not like it, but jewelry has actual value to humans.
It's no coincidence if you look at a list of the wealthiest families, a large number of them trade in luxury goods.
To paraphrase Veblen humans have a profound desire to signal social status, for the same reason peacocks have unwieldy tails. Gold is a great way to achieve that.
On the other hand, BTC lacks all these attributes. Its value is largely based on common perception of value. There are a few fundamental drivers of demand:
Apart from these, it's hard to argue that BTC will retain value throughout some sort of economic catastrophe.

BTC is really risky

One last statement from Michael Saylor I take offense to is this:
“We feel pretty confident that Bitcoin is less risky than holding cash, less risky than holding gold,” MicroStrategy CEO said in an interview
"BTC is less risky than holding cash or gold long term" is nonsense. We saw before that BTC is more volatile on face value, and that as long as the Fed isn't run by spider monkeys stacked in a trench coat, the inflation is likely to be within reasonable bounds.
But on top of this, BTC has Abrupt downside risks that normal currencies don't. Let's imagine a few:

Blockchain solutions are fundamentally inefficient

Blockchain was a genius idea. I still marvel at the initial white paper which is a great mix of economics and computer science.
That said, blockchain solutions make large tradeoffs in design because they assume almost no trust between parties. This leads to intentionally wasteful designs on a massive scale.
The main problem is that all transactions have to be validated by expensive computational operations and double checked by multiple parties. This means waste:
Many design problems can be mitigated by various improvements over BTC, but it remains that a simple database always works better than a blockchain if you can trust the parties to the transaction.
submitted by VodkaHaze to badeconomics [link] [comments]

Open Marketplace by Particl

Hi fellas, this is my first post on the darknet. I read today about the Empire Market and decided to post here about a tech that might help to end this charade of constant exit scams.
My post is about a DLT-based open source decentralized marketplace that will hopefully initiate a paradigm shift in the free and private trade between individuals and ends the exit-scams and leaky databases problem once and for all.
It is called the Open Marketplace V3.0 and is set to be released after 3 years of hard development work by Particl Project, including one year of public beta testing.
My personal belief is that they are releasing to the world a game-changing/breaking product. At minimum, due to the open source nature of the project, this is a proof of concept that is bound to shift the global eCommerce paradigm into DeCommerce.
I hope my own description below of the marketplace and its technology will fuel your interest to read more about it. My even bigger hope is that some of you will decide to become first-hand beta testers as soon as the Open Marketplace v3.0 hits the testnet (eta: a few weeks).

The marketplace:
The Open Marketplace is designed to be private by default and decentralized with no middlemen/intermediaries whatsoever. The trades are protected by two-way automated escrow via smart-contracts that de-incentivize and penalize dishonest behavior on both sides.
The Open Marketplace takes no sales commissions and charges only a tiny listing fee (<0.01$) to prevent listing spamming. All the marketplace generated fees go to the nodes that provide the hardware infrastructure for the p2p network to operate. The nodes can be public or you can run them as Tor hidden services.
The V3.0 that is set to be released will be the first version open to the wider public. It will allow anyone to create easily a decentralized personal storefront or a community market or simply buy and sell goods on the already existing markets. The user-created markets/storefronts can be visible on the marketplace if the access key is publicly announced or absolutely invisible to anyone that doesn't know the access key (held by the creator). This is an intentional privacy feature and simply put without going into many technical details, if you dont have market access key there is absolutely no way to see/detect that some market exists.
The technology:
The Open Marketplace is crypto-agnostic and currently supports payments in BTC, PART, ZCoin (DAI, NIX are next in the pipeline and many more to come). It uses as a settlement layer its native blockchain, which is an up-to-date Bitcoin codebase with added privacy features like CT, RingCT (up to 32 mixins), Stealth addresses, etc. These privacy features are used in combination to keep the financial data like escrows, transactions, etc private and most importantly un-linkable to the actual market buys/sells.
For the actual user or markets related data exchange like posted listings, buy/sell flows, encrypted user communication, built-in cryptocurrency exchange, etc, the Open Marketplace uses a custom Bitmessage variant called SMSG, which allows metadata stripped encrypted data exchange. Last but not least the Open Marketplace client has a built-in option for using Tor network via proxy.

The important people:
The cypherpunks behind Particl's Open Marketplace have been passionate pioneers and OGs in the privacy DLT field. For example, they were the first ever to implement features like RingCT, Bulletproofs, PoS, cold staking, etc on a Bitcoin codebase. Their privacy features implementations have been audited successfully by several respectable academics and security R&D providers, like QuarksLab.
The team has been so far focused on building without any marketing and thus have remained intentionally in the shadows but the latter is planned to change with the v3.0 release. One of the steps towards that will be the initiation of the long-planned Vendor On-boarding and Outreach Program and the release of the Particl Academy, an easy to understand and learn about the project portal.

I am a passionate freedom and privacy advocate that discovered the project 1.5 year ago and since then has become a member of their small but like-minded community ([email protected]/discord).
submitted by Bakounin to darknet [link] [comments]

Gridcoin "Fern" Release
Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that.
Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap.
We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout.
Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.



Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now.
Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date.
The transition height is also when the team requirement will be relaxed for the network.


Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.


The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use.
There are so many goodies here it is hard to summarize them all.
I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures.
The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!

Summary Changelog



Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.







As a reminder:









Detailed Changelog

[] 2020-09-03, mandatory, "Fern"





submitted by jamescowens to gridcoin [link] [comments]


Thai Nhat Minh | Stably:
First of all, can you have a brief introduction about yourself as well as about Chromia? Henrik_hjelte, Sergelubkin
Henrik Hjelte:
Hello. My name is Henrik Hjelte. I am Co-Founder and CEO of Chromia.
I have more than 30 years of experience in programming and a degree in Economics from Uppsala University.
BTW economics and computers = blockchain, so finally found a job that fits me.
I was introduced to the blockchain by the leader of the colored-coins project Alex Mizrahi in 2013
Colored coins project was a very influential thing
It was the first way for user created tokens
bolted on to the only blockchain at the time (almost) bitcoin
We started ChromaWay 2014, with Or Perelman too, to explore if the world was interested in “tokens” and those kind of applications
We worked with enterprise blockchain for some time, but now we are focused on Chromia, a new public platform for mainstream decentralized applications using relational blockchain technology.
Ok, maybe I should tell something about Chromia and not myself too.
Chromia is a better blockchain for building decentralized Apps.
better because it follows the “normal worlds” way of managing data.
A little history: I found a text/description to paste:
Chromia is a brainchild of ChromaWay. ChromaWay has a long record of delivering pioneering projects around the world. We issued Euros on the Bitcoin blockchain with LHV bank, allowed investors to invest in startups in a wholly decentralized way with Funderbeam, digitized the title transfer process with the Swedish land registry, and mediated the green bond market. ChromaWay’s core team created the world’s first protocol to issue tokens already in 2012, when blockchain was called “bitcoin 2.0”. Then ChromaWay introduced the relational model to enterprise blockchains with a consortium database called Postchain. Now Postchain is going public as the foundation for Chromia, a better blockchain for building decentralised Apps.
Chromia is a new public blockchain based on the idea of integrating traditional databases, Relational databases with blockchain security. Chromia is a general purpose blockchain with full smart contract capabilities, just that it is a lot easier to code, even complex applications. You code with an easy to learn new programming language that combines the power of SQL and normal languages but makes it secure in a blockchain context. Up to 1/10 the code-lines vs other blockchains.
If you don’t believe me, check this blog (later, stay in the chat):
The aim of Chromia is to combine relational databases, which exist in every kind of organization, with blockchains. We want to provide a platform for our users to develop totally decentralized apps securely. Our goal is for Chromia to be seen as the number one infrastructure for decentralized applications.
Think about it: blockchain is about managing data (in a shared context).
And… What do we use to manage data? A Database!
Sure! My name is Serge! And I work in Chromia marketing department. Also, I help coordinate various projects inside the company
My background is in Economics and Marketing
Thai Nhat Minh | Stably:
Question 1️⃣
DApp is currently mainly concentrated in the field of games, and its life cycle is basically short, just like the Crypto Kitty is only hot for a while, how to dig the application of DApp in more fields and how to improve the utilization rate of DApp? u/henrik_hjelte u/sergelubkin
Good one, let me answer
Gaming is quite a challenging target because good UX is expected, it needs to be fast, responsive, etc. If we can do that, then we can also do all sorts of other stuff.
Also, it lets us experiment with things without a lot of hassle, it’s easier to get users, and so on. It’s also a growing niche within blockchain. You can check our latest game, Mines of Dalarnia
We also have Enterprise projects already, for example Green Assets Wallet that already launched on the first Mainnet version called Bootstrap Net,we also have built on our tech, more projects like non-profit review platform Impactoria, public land registries, medical projects and so on
Also don’t forget about our fully decentralized social network/forum that is live already on the testnet
Thai Nhat Minh | Stably:
Question 2️⃣
How will dapp face the world change after the epidemic? u/henrik_hjelte u/sergelubkin
Henrik Hjelte:
Nobody can say for sure, but maybe people will tend to be online more than offline, so demand on online products and dapps as well will increase.
I just came in from an internal demo of a secret project we do, and it can be seen as a way to hang out online (a bit cryptic answer)
There are also interesting use cases of dapps in the medical field.
For example, we participated in the world-wide hackathon Hack for Sweden. Where our submission was to create an app on Chromia blockchain that increases the coordination between countries and hospitals especially during the hard time and COVID19.
Chromia wants to help the European Union (and the world, but we saw problems in the EU…) and its citizens to provide transparency over the necessary medical and protective devices and appliances of which we see shortage during this emergency crisis.
You can watch our promo here
For me it was a fun Hackathon too because for once I got the opportunity to code… I told everyone else I will not do any bossing…
We try to continue this path on medical applications a bit.
Thai Nhat Minh | Stably:
Question 3️⃣
DApps are still not directly embedded in mobile phones like Apps at this moment, and DApps have also been flooded with bet content. How can guests increase the use of DApps and lower the threshold for using DApps? u/henrik_hjelte u/sergelubkin
The answer is — better User Experience. We believe that in order for a DApp to be usable and become more widely accepted it has to feel like a normal App. A DApp needs to have quick transactions, scale well & shouldn’t require users to pay for each transaction. This is something that is possible now with using Chromia. It’s an extremely exciting time since we are going to see a new generation of DApps.
On top of that, we think that we might have an ace coming up. We have built a game to demonstrate the powers and possibilities of Chromia. A little bit about the game: In Mines of Dalarnia (, players get to explore the vast expanses of interplanetary treasure mines. With an innovative Dalarnia Token system, players can purchase virtual mining plots, and put them up for rent into the community, allowing for real-estate tycoons to earn more Tokens. Mining plots can also undergo their own upgrades, making them more lucrative to explore, as well as a hot property for rental by miners. The game takes advantage of these NFT-based tokens to securely track exchanges, and provide a sense of ownership and wealth to players as they grow their mining and resource empire.
Watch our trailer and sign-up for the TestNet on the website!
Thai Nhat Minh | Stably:
Question 4️⃣
Many practitioners think that the main reason for restricting the development of DApp is “incomplete infrastructure”. How effective is the current “cross-chain” and “side-chain” solution? u/henrik_hjelte u/sergelubkin
Our infrastructure resembles Alibaba Cloud, so a DApp developer just goes and deploys his DApp’s blockchain into it, it’s easy. Also our language Rell is more robust than any other blockchain programming language.Or Azure or AWS
Rell combines the following features:
  1. Relational data modeling and queries similar to SQL. People familiar with SQL should feel at home once they learn the new syntax.
  2. Normal programming constructs: variables, loops, functions, collections, etc.
  3. Constructs which specifically target application backends and, in particular, blockchain-style programming including request routing, authorization, etc.
Rell aims to make programming as convenient and simple as possible. It minimizes boilerplate and repetition. At the same time, as a static type system it can detect and prevent many kinds of defects prior to run-time.
Maybe Henrik wants to add something. :)
Henrik Hjelte:
Yes, I can add some thing
Consider again the real /normal world. What made the apps you use every day? Behind the bank app is a relational database. Web 1.0, “shopping on the internet” was a relational database hooked up to a webpage.
web 2.0: Thefacebook was PhP and MySQL hack
again, a relational database.
So, we aim to make it just as easy to do decentralized apps as normal apps.
Also “the cloud” inspiration is more normal. In Chromia, the dapp developer pays for hosting the application (normally). Not the USERS.
No gas,this is a big usability improvement.
Thai Nhat Minh | Stably:
Question 5️⃣
There are many DApp development platforms on the market. What are the competitive advantages of Chromia? It can be explained in terms of development cost and ease of use that everyone is more concerned about. u/henrik_hjelte u/sergelubkin
Henrik Hjelte:
This what I’m talking about. I think “Ease of use” combined with “Power” is our biggest strength.
Easiness is our core feature thanks to the relational database aspect of our system. Relational databases are run by 85% of the enterprise market at the moment.
And used in 100% of all organizations.
The largest vendor on that market Oracle, has a bigger market cap than bitcoin,
So, this makes it easy for enterprises to integrate our tech stack to their normal systems without the need to redo them, like in most cases where blockchain pilots have failed.
That’s partially why we had success with enterprise customer which are live in the Chromia network.
And: there is a large set of features that relational databases have that alternatives (noSQL) do not have or do not do as well.
And blockchain is very primitive compared to that.
Data indepence, mathematical foundations etc. Large books have been written about it…
On Chromiam It’s very easy for developers to deploy DApps because they already know SQL-style programming. Keep in mind that we worked with customers and developers to build our tech stack while solving problems for them. We didn’t build something unneeded, we had proof of validation from the market.
SQL is top 3rd language in the world (after HTML and javascript).
source: stackoverflow survey 2019, among 90 000 developers…
Top 4 used databases: different flavors of SQL (relational databases)
So, they are used for a reason: Ease of use/programming, power etc.
Also, Rell is our language, is statically typed (means bugs are discovered when programs are written rather than we they run). It is also more compact, up to 1/7 of the code lines of SQL. And have “normal” programming constructs + blockchain programming built in.
Because we require both relational database properties and more security than SQL, currently Rell is the only choice. It is really easy to learn, please go check
Chromia also provides news to the database developer community….
millions of developers in potential.
OK, bear this in mind when you wonder how we can compete with blockchain X… Blockchain X is a fart in the ocean compare to the SQL world 😊
Bach Tuyet
You have organized many AMA sessions to the international community in general and Vietnam in particular. What do you most want to get after AMA sessions from the community? u/henrik_hjelte
I’ll take this one:) our goal is to grow the community
  1. We want people to join our channels such as telegram, twitter, email also our decentralized forum and participate in discussions
  2. We want people to try our dapps such as Mines of Dalarnia
  3. We want to get feedback and understand the most important issues people care about Chromia and the blockchain industry in general
  4. We want to get more developers building on top of Chromia
What was your motivation for creating RELL and not use other languages? What benefits? Why name it RELL also?
Henrik Hjelte:
We have a private/federated relational blockchain called Postchain, and it allows SQL. But that can work in a small environment when you know all parties, and if you are really careful in checking code. But not for a more secure, distributed on the web setup, so we had to make it more secure (Deterministic, statically typed).
In the process, we also took the opportunity to make it cool and nice.
Also: it is simply not possibly to use evm, jvm, or web assembly. We need/want a database in the bottom. Postgresql is our virtual machine. You do not reimplement that…. 10+ years codebase….
Being part of the gamer community, I would like to know what you would think about collaborating with a MOBA, RPG or Arcade game or some kind of project?
Henrik Hjelte:
We are already collaborating with some smaller studios. For bigger fish, we want to show them what is completely unique and visionary with Chromia, and we think we need various examples. So, first arcade game MoD (linked above) is one example, it is not the full potential or anything but a start. In this summer, krystopia 2 a puzzle game from Antler Interactive will be released.
What is even cooler is the “demo project” we do together with them, where we will show how a mutliplayer game with real blockchain features will work.
I just saw it an hour ago and was blown away
OH, and there is another studio releasing something very cool. Full logic on chain strategy game. Chain of Alliance.
oyibo pepper:
Do you encourage HACKATHON programs for intending Developers to test their skills and build on RELL
Yes, you can, but you will need to change your avatar 🤣
Seriously, we are growing our Chromians community if you want to become one please ping our admins in Chromia telegram group.
Also, we are planning virtual hackathons soon, please subscribe to stay updated
Infinite Crypto:
Since the Chromia project is currently working on the Ethereum blockchain ERC20 standard!
But we know that there are a lot of scalability issues with Ethereum, so why would you choose the Ethereum blockchain over other scalable blockchains? Do you have any plans for Mainnet launch of Chromia?
Henrik Hjelte:
ETH is just used in a pre-phase for tokens. We will have our own mainnet tokens interchangable with ETH.
Oyinbo pepper
What’s CHROMIA SSO and SDK, how can I get started
Henrik Hjelte
Both are 3 letters. That is what they have in common.
SDK = software development kit, check docs on
SSO = single sign on. A unique UX improvement. You approve an app in your wallet (vault) with super ease. no need to remember codes
We have a fundamentally different model from bitcoin and ethereum and the likes. The blockchain is not run by anonymous computers in basement and student dorms across the world. We have more of known identities, so 51% attacks is protected not by PoW/PoS but other consensus. Please see our whitepaper. Note that we are not noobs when it comes to this, our CTO Alex has published papers in academic journals on consensus etc. from 2013, and done several important ideas for blockchain. Sidechains we think he was first with, tokens too.
Sheron Fernando:
Is there any plan to makes partnership with local cryptocurrency developers from each country to make $CHR usage more worldwide?
Yes, we are looking for cooperation with more external developers. Send me a message if you are interested in developing something on Chromia.
What are the underlying problems in the Dapps today that can be solved with the Chromia protocol?
  1. Scalability — on Chromia your dapp can have unlimited numbers of users thanks to parallel scaling
  2. Easiness of use — you don’t need external wallets, no need to buy crypto to pay for gas etc
  3. Cost — in general to deploy the dapp and to use the dapp
Marcel Lagacé:
Why build this platform? What is Chromia mission? What are the most prominent features of the platform? Can you clarify the use case for this feature?
Henrik Hjelte:
We build the platform to fix the problems with blockchains, that we ourselves have experienced since 2014 (before ethereum existed).
Can you tell us about Chromia developers? How motivated and experienced are they to always deliver the best products?
Henrik Hjelte:
I can tell you that we recruit developers that are really good, from all parts of the world. Vietnam has been a hub because we found many good, so in Ukraine.
How can we say “we have so good developers”? First one thing that is a bit different is that we are pretty experienced in leadership team of development. I do not code much anymore since I’m a CEO. But I do have now over 30 years of experience. Got published and was payed when I was 15. First full-time professional developer job at 18. Have released open-source projects used by 10: s of thousand developers.
And Alex, our CTO is Extremely good. That is why I recruited him to my old startup 2006 or so… So: we have experience to sort out good developers from bad.
Marcel Lagacé:
Does Chromia staking model is different from other staking platform??
What are the beneficial advantages of chromia staking system?
The main difference is that we have independent Providers, entities that are not connected. These serious players are exchanges, data centres, professional staking companies. They provide a backbone of the ecosystem and host dapps. Like Amazon servers in the cloud. They cannot have stake bigger than the maximum thus they can’t control the network. This is probably the main difference with classic DPoS networks
Nguyen Duy Bao:
A lot of people will want to know what the strength of Chromia is but I want to know the weaknesses and problems Chromia faces ? How do you plan to solve it?
Henrik Hjelte:
A weakness I guess is weak compared to “competition”. And there are some blockchain projects that got crazy amount of funding. So how can we compete with that, when they can hire more developers for example? Well here is what experience comes into play: More developers does not always increase productivity a lot, it is diminishing returns. You can see many large projects, with 100 of developers fail miserably with no results.
And actually, sometimes true with marketing spend too. It is generally good with money, but if you are a bit clever you can compete also on marketing with less money than your competition.
Please follow Chromia on Social Media:
Decentralized Social network Chromunity:
Free-to-Play Blockchain Game Mines of Dalarnia:
submitted by dam30 to Teamchromia [link] [comments]

Peercoin v0.9 (Codename Strider) Released - Includes Update to PoS Reward Economics - Hard Fork is June 8th, 2020 - Upgrade Today!

Peercoin v0.9 (Codename Strider) Released - Includes Update to PoS Reward Economics - Hard Fork is June 8th, 2020 - Upgrade Today!
NOTE: If you are new to Peercoin, check out the Peercoin Primer, a short 5 part video series covering the basic fundamentals of Peercoin.

Peercoin v0.9 Released!

We are pleased to announce that after many hard months of work, Peercoin v0.9 (Codename Strider) is complete and a hard fork is planned for Monday, June 8th, 2020 at 12:00:00 UTC. You must upgrade your wallet client before then!


Peercoin release v0.9.0
  • RFC-0019: PoW Block Spacing
  • RFC-0018: PoS Rewards Adjustment
  • RFC-0017: Limit Effective Coinage to One Year
  • RFC-0015: Reduce Time Drift
  • allow staking=0 command to disable minting
  • ability to filter out mint transactions in the QT wallet


While Peercoin v0.8 (Mantis) was largely about modernizing the codebase and improving the technical capabilities of the reference node software, the v0.9 (Strider) development cycle was about the economics of the Peercoin cryptocurrrency.
Both the PoW and PoS aspects of the network have been modified. Proof-of-Work changes are rather minimal; in summary target block spacing has been set to 60 minutes, rather than having dynamic PoW block spacing target. Block spacing is currently approximately 60 minutes anyway, so this may not sound like a big change, but it stops some PoW pools from trying to game the system. By making PoW more predictable, RFC-0019 brings inflationary stability to the overall system.
That change is minor when compared to the modification of the Proof-of-Stake side of the system. Some of you may have been following the discussion on RFC-0011, which was ongoing for over a year, and you may have noticed that RFC-0011 was rejected about two weeks ago and replaced with RFC-0018.
In my personal opinion, RFC-0011 is a great idea, probably the best idea thrown around here in the last couple of years, but ultimately it's too complex and we could not get consensus about it. The gist of both RFC-0011 and RFC-0018 is that the Peercoin money supply inflates at a rate of 1% on paper, but we are nowhere near that in practice.
In the old system, in order to have PoS inflation at 1%, a full 100% of all peercoins would have to start minting and solving blocks. This is simply impossible. In reality, over the last couple years Peercoin's PoS inflation has only been between 0.10% and 0.20%, which is far from the "promised" annual 1%. Due to the very rough history of this beautiful blockchain, namely the closure of btc-e, dozens of exchange hacks and closures, as well as a couple of de-listings, we are in a situation today where nearly half of the monetary supply has not been moved for over two years and we can consider those coins lost for all intents and purposes.
The basic principle of RFC-0011 was the following: the Peercoin network promises a steady inflation of 1% on monetary supply, and if you want a cut of it: mint. In essence, if only 20% of all peercoins are minting, the effective reward for active minters would be closer to 5% per year. However, the problem with this scheme is that minters would try to game the system and only mint when minting participation is low. Thus, we came up with RFC-0018, which yields similar results, but keeps the reward calculation simple and prevents gaming of the algorithm. You can read more about the change here.
Long story short, the network will reward active minters more, while keeping the overall inflation around 1%.
Accompanied with an expected inflation drop from increasing PoW hashrate, overall monetary inflation will largely remain unchanged, and will be more stable.
Other changes are minor and do not change the behavior of the network. RFC-0017 is just a consequence of RFC-11, and it stops minters from going offline for longer than a year and coming back to mint. We did not see this as fair, so the coinage counter is reset after a year now. Limiting coinage disincentivizes extremely long term periodic minting, thereby making continuous minting more attractive.
-- Peerchemist, Peercoin Project Lead

Upgrade Instructions

Before installation, make sure to backup your wallet from the main menu.
The v0.9 client can be downloaded from the wallets page of For users upgrading from v0.8, upgrade instructions can also be found on that page.
For the minority of users that may have skipped v0.8 and are upgrading from v0.7 or earlier, please check these additional instructions from the previous v0.8 release thread as you will need to go through the additional process of rebuilding your block database. If you need help with installation, leave a comment below.


To stay informed as we get closer to the hard fork date, you can follow the latest Peercoin news on our forums, our Twitter, or Reddit.
Other places to follow us:
Facebook LinkedIn BitcoinTalk Youtube Medium
Don't forget you can see the latest updates using the Blockfolio and Delta Apps!
Download Link:
Final reminder: The upgrade deadline is planned for June 8th, 2020 at 12:00:00 UTC
submitted by Sentinelrv to CryptoCurrency [link] [comments]

BTC and BCH To Be Sued For Software License Violations

Anyone care to explain how BCH and BTC are not truly fucked now?
Software licenses don't lite.. and neither does source code and software registries... sounds like the BCH and BTC fraudsters are about to be finally busted....

Read This!!!::

“Forking” a software branch is allowed under the MIT License. Both Litecoin (LTC) and Ethereum (ETH) present “forked” codebases, derived from Bitcoin. CoreCoin, BTC, differs in the sense that it both copied the database [3] and sought to pass off the new system as the old or original.
To give an analogy, the Bitcoin software that was released as an implementation is an open-source software under the MIT License. Linux and OpenOffice are each open-source products. If I was to write a novel using Linux as the operating system and OpenOffice as the editing platform, the software remains open-source, but the product of my work does not. In other words, I retain the copyright in the works I create using the open-source software. Bitcoin is a distributed registry. Tokens are not distributed as they reside in individual wallets, that are controlled by individuals around the world that use the Bitcoin system. The tokens are distributed in a peer-to-peer manner, from individual to individual. The registry of the movement is a separate peer-to-peer network, that acts within the hybrid system that is Bitcoin. The registry [4] presents the distributed ledger. And the distributed ledger is a database.
As the sole creator of Bitcoin, I own full rights to the Bitcoin registry. People can fork my software and make alternative versions. But, they have no rights to change the protocol using the underlying database. I was explicit when I said so by putting forward reasons not to fork the database. Yet, both Bitcoin Core (Core) and Bitcoin ABC (ABC), global partnerships under law, have sought to use my database without authority. Rather than seeking licences, they have sought to attack my character and impugned me. This year, I am taking charge and control of my system [5]. Those involved with the copied systems that are passing themselves off as Bitcoin, namely BTC or CoreCoin and BCH or BCash, are hereby put on notice. Please trust me when I say that I’m far nicer before the lawyers get involved."

Anyone care to explain how he is wrong or lying about this? I know quite a bit about open source software and the laws/rules regarding them and from a legal standpoint it looks like BCH and BTC are about to be truly fucked.
Am I wrong?
submitted by mywebguys to bsv [link] [comments]

Recap of Chromia AMA with the CEO of Chromia, @henrik_hjelte on BithumbGlobal telegram community dated 14.04.2020.

The AMA was moderated by u/Sidonpee.
Let’s start with the introduction question:
u/henrik_hjelte Can you introduce yourself to the community? What is your background?
Henrik Hjelte
I’m the CEO of ChromaWay, the company that started the Chromia project. My background is 30+ years as a developer (got payed first when I was 15), then studied Business and other things (politics and philosophy). Worked as Finance and IT consultant. THen wanted to be an entrepreneur. started a “web 2.0” startup about a free-speech internet. Hired our current CTO as a developer. THen joined his colored-coins project, the first token protocol ie the start of blockchain in 2012.
Sorry. I’m now 50 years old, the math didn’t add up. That is why I’m the CEO and not CFO.
Q1. What is Chromia? Can you tell us the technology behind it and the features that makes it unique?
Henrik Hjelte
Chromia is a new public blockchain based on the idea of integrating traditional databases, “Relational databases” with blockchain security. In the normal world outside blockchain, there is one technology that is in 100% of all enterprises and powers almost all webpages. It build Facebook, SAP, banks, blogging platforms. It is the relational database, or SQL database. Has been used for 30+ years and is still dominant with 85% market share. Why are people using it (NoSQL has been around for 15+ years)?
Because it is the best way of managing data known to mankind. Now what is blockchani? It is a way to manage data that is shared. So if you agree that blockchain is about managing data, a relational database should be an obvious technology. Chromia is a general purpose blockchain with full smart contract capabilities, just that it is a lot easier to code, even complex applications. You code with an easy to learn new programming language that combines the power of SQL and “normal languages” but makes it secure in a blockchain context. Up to 1/10 the code-lines vs other blockchains.
Q2. I often see Chromia and ChromaWay being used interchangeably, what is the relationship between the two?
Henrik Hjelte
The idea for Chromia and parts of the codebase originated from the company ChromaWay. It is actually one of the first blockchain companies, we had a project for tokens before ethereum called the “colored coins” project that led to us starting a company with a name take from the greek word for color. In 2015 we did what is now called stable-coin, EURO payments based on tokens on a public blockchain (tokens on bitcoin). It was for a bank LHV in Estonia. When we need to quickly find information, we could not search the blockchain and instead started to dump everything to a relational database, and then the idea started to grow to build a blockchain around this. So we did a private blockchain, intended for usecases in land-registration, banking and more. And then came up with the idea of doing a public blockchain for it.
ChromaWay is the company that ideated Chromia and provided the first open source code for it. The Chromia pre-sale of tokens is now funding the development of Chromia, which is done by ChromaWay. When Chromia is released as a decentralized network, it will not be governed or run by ChromaWay. Of course we know it has to be decentralized, we understand the virtues of decentralization since 2012 when our CTO did the worlds first code for tokens, then started an open-source project which even inspired Vitalik (who soon quit and did his own thing). ChromaWay as a company will take a role as providing optional support and maintenance of Chromia projects (open for competition by other players).
Q3. What’s the usefulness of $CHR token in Chromia ecosystem?
Henrik Hjelte
CHR can be used to pay for running dapps (normally by the developer of the dapp, not users). It can also be used as a mean of exchange between dapps, and to provide collateral/stake for providers (the ones running the blockchain), incentivizing good behaviour.
Q4. What are the major milestones Chromia has achieved so far & what are your plans for 2020?
Henrik Hjelte
We have released Rell, the new programming language that is needed, and supported tooling (online Development Environment, downloadable IDE, documentation). We have release the first testnet in december, and at the same time another company 4irelabs has done the first dapp running on testnet. They could take our old code (done as a private blockchain), learn our new language Rell and port it to Chromia. That project is the Green Assets Wallet, green bond environmental impact reporting, run by a non-profit and with banks and institutions as users.
Plans for 2020 is to both release a series of dApps to showcase how fantastic Chromia is, as well as continue to develop the platform. And when it is secure and good enough, we will release mainnet.
Dapps are now being made by us as well as others. We do a decentralized social network framework call chromunity, now release to testnet. If is really cool, users can vote over moderators, and in the future users might even govern the complete application, how it can be updated. This is a great showcase for Chromia and why we use the slogan Power to the Public.
Games coming are….
  1. Mines of Dalarnia (by Workinman Interactive). An action game in a mine with blockchain rental of plots and stuff.
  2. Krystopia 2, novas journey. A puzzle game done by Antler Interactive.
  3. An indie game (not done by us so I don’t know how much I shoiul;d menton), but: it is a strategy game with FULL-LOGIC ON BLOCKHCHAIN yes ubercool that is why it is in caps
  4. A secret demo-project that we do together with Antler to showcase the technical potential of Chromia platform.
More comin in 2020: Other dapps from other companies, one in impact-tech
Games is a great way to show scalability and features BTW.
I didn’t mention that Chromia is very scalable (everyone says that). But it is true, and with no tradeoff vs decentralization
well, but I can also see enterprise projects going into more of public blockchain direction and hybrid, and there I think Chromia can really shine
Q5. Revenue and adoption are the main points of all projects, can you tell us your Business model and how you generate revenue?
Henrik Hjelte
Chromia itself is a public network with no intrinsic business model, but participants in the network has. For example Providers make money from supplying quality hardware running dapps and the core software, dapp developers have individual business models.
I already told about about ChromaWay/Chromia, but ChromaWay the company can provide support/maintenance and various services and add-ons for Chromia. It is very similar to how normal open-source vendors make money.
Still up to competition from others, and without control over the Chromia network. We need it to be independent, otherwise it has no value.
So it is sound business to have it decentralized as well, who would care otherwise?
Q6. Regarding Chromia’s blockchain game (Minesofdalarnia), I’m quite sure that vast majority of game lovers would be anticipating for it release, could you please share with us the likely date it will be released?
Henrik Hjelte
Yes I can
We have made very good progress recently, and I can happily share that MoD is planned to be released now in Q2.
Meanwhile you can check the Mines of Dalarnia Social Media page for recent updates on the game . We publish development updates there often.
You can also sign-up for early access on 😉
Q7. Recently Chromia welcome Malcolm Lerider who was formally a Senior R&D Manager for Neo Blockchain as its new team and family member. When he was with Neo, he worked together with the community and was able to build the project from a top 50-something market cap project to a top 5 market cap project. Should we be expecting a replica of this at Chromia in the nearest future?
Henrik Hjelte
Yes. we are very excited to have Malcolm on-board, he is very knowledgeable in the area, and his expertise will definitely help with achieving that. Malcolm recently published an article where he introduced himself as a new member of Chromia. You can read it over here, if you haven’t already:
Q8. Green Asset Wallet is absolutely an amazing starter in the Chromia blockchain! I would like to hear how you guys see the future business development possibilities in the next /6/12 months? Are there specific business areas, geographical locations, which you want to focus on most?
Henrik Hjelte
Thank you, yes, it is nice to have a project that is enterprise, and green too as the first one.
We are working both to reach out but also support inbound requests for projects, I shared some above.
Sometimes with business development, ChromaWAy might find a customeprospect but we don’t know where it will end. We think however, and Gartner too, that enterprise blockchain is gradually looking more at public blockchain projects.
I think DeFI, tokenization of assets and things like that is interesting.
Also, hopefully someone will be inspired by our solution to a free, open, user-governed decentralized social web, what we are now showing with Chromunity. Jack Dorsey, are you listening?
We don’t have a particular geographical focus though, and really it is a generic platform use-case agnostic.
We use games to show potential and scalability, but who knows maybe other applications will be more. It is not only up to us.
Q9. Who are Chromia’s strategic investors and partners? What criteria/ process do you follow in evaluating your partnership deal with them?
Henrik Hjelte
We have some strategic investors and partners that have helped us during the way, I think maybe I should not mention them here with the risk of forgetting some of them, and I have no time to check if we should mention them, We (and the partner) look at how we can help each other on a case by case basis. There is no simple scorecard that we can follow.
We try to avoid vanity partnership deals with no real meaning
Q10. Why did Chromia develop a new language called Rell (Relational language) for dapp
Is the development of this new language really necessary?
If yes, what are some of its unique features that cannot be found in other existing languages/environments?
Henrik Hjelte
Yes it was necessary. We need the features of relational alegbra. It is is a mathematical basis, very similar to logic, that has only had basically one implementation (SQL). But SQL was not secure enough and lacked features that can be used in a shared context like a blockchain. Everything needs to be secure. Also we wanted to add blockchain features, and make it look more like “normal programming”. Now some of the readers might ask? Can’t you do this on the EVM? No. Ethereum does simply not have anything similar to a relational database, and it would be technically infeasible.
Some others may ask? How can you compete with the EVM /pet-project that have soo many developers etc…?
My answer is : we are building on top of a virtual machine called Postgresql. Check how much time, optimization and money has been spent on that virtual machine…
I think it is 20 years or more of development time, maybe more.
Static typing is one feature we add that SQL doesn’t have (you can detect bugs at compile time)
What have been the major obstacle Chromia has faced in the past years while developing its idea?
Whats the benefits for developers at Chromia? Why should we use Chromia instead of your competitors?
Henrik Hjelte
Obstacle: Technology/software developement is hard sometimes, difficult to predict when things are ready.
Major benefits for developers: A LOT EASIER to code COMPLEX applications. I’m serious. If you are frustrated with blockchain development, take a look at the ease of use of Rell/Chromia
DeFi is projected to buzz up in 2020 and is on everybody lips, what ROLES does Chromia play in the innovativeness and future of DeFi and how does it spearhead adoption of DeFi using blockchain solution?
Henrik Hjelte
Finance would be almost unthinkable without relational databases, the power core banking and more. An exchange is a table of bid and ask, and you match them. This is very easy to do with our tech.
If any Dapp is created on Chromia Blockchain! Then is there any Gas fees charged by Chromia? Whats the concept of fees for Dapps on Chromia Blockchain?
Henrik Hjelte
No gas per user fee. The application pays for hosting, like a cloud. Normally the developer, unless the developer hands over the governenace of the application to someone else (maybe the users).
If any Dapp is created on Chromia Blockchain! Then are there any Gas fees charged by Chromia? Whats the concept of fees for Dapps on Chromia Blockchain?
Henrik Hjelte
No gas per user fee. The application pays for hosting, like a cloud. Normally the developer, unless the developer hands over the governenace of the application to someone else (maybe the users).
Most blockchain projects have donated to COVID-19, but no news from Chromia. How will you contribute to fight COVID-19?
Henrik Hjelte
I had to answr this: I spent my free weekend time on a covid-19 hackathon the other week to do a solution to share medical equipment across countries. It is on our facebook I think u/anastasiazudina maybe you can share
We want to do our part for the ongoing covid19 crisis. Therefore, we were participating in the critical initiative HackTheCrisis. During the virtual hackathon, we tried to find good solutions for the new unique challenges that we now as a society are facing.
Chromia creates a new lightweight programming language called RELL. How is this different and better for programmers than other popular language like Solidity, C++ and Java?
Henrik Hjelte
When you think about a large Java project done for say a bank. Ask the developers what OTHER thing they use? DO they ONLY use Java and store files on a server? Or do they also use a database. You will find that in 99.9% of cases they ALSO use a relational database. No one would EVER think about doing a solution to manage data with ONLY Java, C++ or whatever.
Alejandro Urich
For the development of the Dapps, do you only support Rell? Is it possible to program in another language that works with Chromia?
Henrik Hjelte
Because we require both relational database properties and more security than SQL, currently Rell is the only choice. It is really easy to learn, and in all cases if we allowed a “normal” language it would miss the feautures of relational databases.
zafer metin
Mr Henrik What are the advantages of Postchain used for Chromia? How is a consortium provided to database management with distributed control?
Thank you for your interest in Postchain uses! We have an article written what answers exactly those questions:
Stay At Home
As I know providers will be chosen by Chromaway, so how is it decentralized due to choice is totally in Chromaway?
Henrik Hjelte
Initial providers. We will migrate to a model where ChromaWAy has no more say than anyone else. But we need to bootstrap and start. Better to choose good initial providers.
David Prince
What is your long-term vision about the industry which Chromia is working at? Are you afraid someday there will be another Project with more innovative technology can replace Chromia?
Henrik Hjelte
Well. Blockchain is about managing data (in a shared context). I’m repeating myself but the market leading (85%) for 30+ years slution to manage data is a relational database. We are now the only relational database + blockchain. Who knows, maybe some better way to manage data will be invented? But even NoSQL who has been around and bark like a little dog has after a decade or more time only 15% market share. I think our tech will stand the mark of time.
The AMA session with the Chronia team has finally come to an end.
We’re greatly astonished having a well-articulated AMA session with Chronia’s CEO Henrik Hjelte u/henrik_hjelte and community/social media manager team Anastasia u/anastasiazudina in the community👨‍💻👌
Also, we are indeed overwhelmed by all our esteemed community members, for your support and enthusiasm for the project.
For more information and to be part of the project, you may join the Chronia’s community here via:
( — Official English Group
The official Chromia community group by ChromaWay. Where dapps thrive!
submitted by dam30 to Teamchromia [link] [comments]

Bitcoin Exchange for Sale!

Bitcoin Exchnage Site for sale!
I am selling Bitcoin to PayPal/Skrill/Other Payment systems.
Why am I selling this? - I need money ASAP and I can't wait month to get money from commissions.
How much can this website make? - You can make up to 10% from every transaction (BTC to PayPal exchange). - At 100 customers per week, it will require less than 1 hour of maintenance (plus ~2 minutes per transaction).
1) CODEBASE: You will get: - entire codebase (frontend & Backend (NodeJS)) - all future updates - Detailed instructions how to set up databse & server - Instructions hot to make 0 - 10% profit (you decide how much) "outsourcing exchange" from bitcoin to paypal. You don't even need paypal account. - I can set up & configure your server
PRICE: $250
2) DOMAIN + SERVER (You must buy CODEBASE) You will get: - Everything in CODEBASE - SEO domain name (6 characters).net, domain registrar account, email used to create account (with password) - Configured Ubuntu 16.04 server with web-app already running (SSL & database & Server security) - Cost of server is $8/month, bulletproof hosting (crypto accepted)
PRICE: $50
3) EXCLUSIVE (You must buy DOMAIN + SERVER + CODEBASE) You will get: - DOMAIN + SERVER + CODEBASE - exclusive rights to use this code.
PRICE: $200
If you are interested, send me a DM. I don't want to publicly post website address.
I can provide proof that I own the site & code.
Escrow payment possible!
submitted by dealercat to OnlineBusiness [link] [comments]

Bitcoin Verde v1.1.0 : Schnorr Signatures

For those unacquainted:
Bitcoin Verde is an indexing full-node, written from the ground up in Java. Bitcoin Verde comes with a block explorer, and a stratum mining pool. While we consider v1.1.0 still a beta release, our public node ( has been stable since January.
Bitcoin Verde is the first to write a Schnorr Signature verification algorithm for Java (using Pieter Wuille's specification) ; if others implementations or wallets need to use our implementation as a reference, it can be located here. Verde's Schnorr implementation has been tested against the same suite of tests as ABC's (Test file located here). We intend to submit a pull request to Bouncy Castle sometime in the future.
Things that are new this release:
Similar to our previous release, Bitcoin Verde is very likely incompatible with Windows. Furthermore, it's an indexing node, and because of that will have more system requirements than a traditional node due to database indexes and the inherent underlying database structure. Our fully synced node is currently using 615G disk space, and 21G of memory. Bitcoin Verde can be configured to run with far less memory, with a minimum around 2G. (Disable UTXO caching, disable TX Bloom Filter, set max database memory to ~1.5G). We highly recommend running BV on an SSD or M2. Traditional HDD drives are awful at random reads, and the last attempted initial-block-download we performed on an HDD took about 2+ weeks to complete.
If you have any problems with your node, please reach out to us at [email protected]. We'd be happy to help and troubleshoot problems. Alternatively, you can report bugs or issues to our github.
We've been diligently working on a mobile wallet based on the Bitcoin Verde codebase. We hope to provide a more modern replacement for bitcoinj, while also supporting SLP tokens. We are also ensuring all Bitcoin Verde SPV code can be transpiled to Objective-C (with Swift Bindings) for use on iOS. Finally, Bitcoin Verde is experimenting with a new message to improve the initial synchronization of SPV wallets called addrblocks, which will greatly improve the ability to validate SLP tokens. Additionally/alternatively, we have been looking at supporting BIP-157 for a more privacy-oriented way to achieve near-instant SPV synchronization; we look forward to sharing these thoughts in the near future.
Again, thank you to the XT team for your support. Another thank you for the ABC team for welcoming us into your conversations, and for helping us understand some of the nuanced aspects of this HF.
To install/upgrade your nodes, clone/pull master at, and reference the README under Installing/Upgrading.
submitted by FerriestaPatronum to btc [link] [comments]

PSA: The Bitcoin ABC Bug Disclosed by Corey Fields Would NOT Have Destroyed Bitcoin Cash (Details inside)

Top posts now on /btc are about the responsible disclosure of a bug (introduced by code refactoring) found in a release of Bitcoin ABC, the most popular node implementation for Bitcoin Cash. The way the tipster handled his discovery went beyond what anyone would be expected to do, and the BCH community is offering gracious thanks, for good reason. However, it's important, in addition to seeking to learn from the incident, to fully understand the dangers and probable outcomes of exploit. The tipster's Medium article somewhat exaggerates this claiming "transacting Bitcoin Cash safely would no longer be possible". That's not right, nor are highly upvoted comments in threads claiming this white hat "saved BCH". Why? Because the EXACT same thing happened to the blockchain now known as Bitcoin BTC or simply Core.
First, a quick recap on the bug. The "SIGHASH_BUG" as the tipster calls it would have allowed an attacker to create a transaction splitting the Bitcoin Cash blockchain into two incompatible chains, due to a validation check apparently removed in the code refactoring. The tipster correctly explains that because blocks are chained together, a difference in any block creates a completely incompatible future chain for any nodes that don't incorporate that change. In other words, all node software must remain in transaction and block lockstep at every point along the way as the blockchain grows. At any point where a difference is introduced, nodes accepting the difference as valid will fork or split from nodes that reject it as invalid. This is not a problem if there are say 100 total nodes and 1 node forks with some difference. The network would hardly notice. However, a substantial number of nodes, say 40 out of 100 would be more disruptive, because a significant part of the network, which underlies a real world economy of users and businesses would suddenly disagree about reality.
As stated the exact same thing happened before. I lived it. I can't recall the exact date, but it was I believe around March 2013. There was only one major Bitcoin blockchain (BTC), and Gavin Andresen was recognized as the lead software developer, along with four others whom he considered his closest peers - Jeff Garzik, Greg Maxwell, Pieter Wuille and Wladimir van der Laan. Mike Hean would have been included in that group but he primarily worked on a separate protocol codebase of his own creation (BitcoinJ). Again, the issue arose from changing the software and issuing a release containing the undiscovered bug. I logged into to see the community in a fair panic. People were posting memes about the Titanic sinking and popping bubbles. There was an urgent stickied alert from Pieter Wuille IIRC acknowledging the trouble with action items for those running nodes. The scene was chaotic but people found Bitcoin was experiencing its first unintentional "chain split".
It was later discovered how the bug came about. Database code was rewritten in a way nodes running oldenon-upgraded versions of the software would reject blocks seen as perfectly valid by those who upgraded. A large portion of (but not all) miners had upgraded when the split occurred. To resolve the issue Gavin Andresen reached out to miners and asked one side (IIRC) to revert back to the older version. This put the network back into agreement, with the forked blocks forever discarded. Two things made the situation quite a non-issue. The first is that (wisely) a prior rule had been introduced that newly mined coins could not be moved (spent) for 100 blocks, which is about 17 hours. This meant no economic activity could possibly have occurred on the "wrong" chain. Second, Gavin, being the upstanding, generous, caring person he is, gave miners on the losing side bitcoins he had sitting in an early faucet (Gavin invented the idea of faucets). So ultimately no harm was done. This is why it wouldn't have been the case BCH would have "died" either if it had actually gone through a splitting action.
A final thing I'll point out is this is a vote in favor of having more than one software implementation. Gavin later discussed this very thing at an MIT Bitcoin workshop. He reflected on a couple key things in hindsight about that bug. One is that even had he not reached out to miners to manually put them back into consensus he said things would still have been okay, because there would have eventually been a longer chain, which is ultimately what Bitcoin respects. Second, he posited this was why having multiple implementations is a good idea. A bug in one version is unlikely to be present in all versions, so a network well diversified is more bug robust, as there is less chance a critical bug affects a majority of the network. BitcoinABC is adopted by about 60% of the BCH network, and about half had upgraded, meaning had the bug activated then about 30% would have split away. However, even in the case 100% had upgraded and the bug activated, it would mean 60% of the network would disagree with 40% (nodes running other than Bitcoin ABC), so there would still soon be a longer chain. Network participants would then need to decide which software version to adopt to put 100% of the network back into consensus. So, again, disruptive, but clearly not "death" or inability to ever again transact.
submitted by cryptos4pz to btc [link] [comments]

A technical dive into CTOR

Over the last several days I've been looking into detail at numerous aspects of the now infamous CTOR change to that is scheduled for the November hard fork. I'd like to offer a concrete overview of what exactly CTOR is, what the code looks like, how well it works, what the algorithms are, and outlook. If anyone finds the change to be mysterious or unclear, then hopefully this will help them out.
This document is placed into public domain.

What is TTOR? CTOR? AOR?

Currently in Bitcoin Cash, there are many possible ways to order the transactions in a block. There is only a partial ordering requirement in that transactions must be ordered causally -- if a transaction spends an output from another transaction in the same block, then the spending transaction must come after. This is known as the Topological Transaction Ordering Rule (TTOR) since it can be mathematically described as a topological ordering of the graph of transactions held inside the block.
The November 2018 hard fork will change to a Canonical Transaction Ordering Rule (CTOR). This CTOR will enforce that for a given set of transactions in a block, there is only one valid order (hence "canonical"). Any future blocks that deviate from this ordering rule will be deemed invalid. The specific canonical ordering that has been chosen for November is a dictionary ordering (lexicographic) based on the transaction ID. You can see an example of it in this testnet block (explorer here, provided this testnet is still alive). Note that the txids are all in dictionary order, except for the coinbase transaction which always comes first. The precise canonical ordering rule can be described as "coinbase first, then ascending lexicographic order based on txid".
(If you want to have your bitcoin node join this testnet, see the instructions here. Hopefully we can get a public faucet and ElectrumX server running soon, so light wallet users can play with the testnet too.)
Another ordering rule that has been suggested is removing restrictions on ordering (except that the coinbase must come first) -- this is known as the Any Ordering Rule (AOR). There are no serious proposals to switch to AOR but it will be important in the discussions below.

Two changes: removing the old order (TTOR->AOR), and installing a new order (AOR->CTOR)

The proposed November upgrade combines two changes in one step:
  1. Removing the old causal rule: now, a spending transaction can come before the output that it spends from the same block.
  2. Adding a new rule that fixes the ordering of all transactions in the block.
In this document I am going to distinguish these two steps (TTOR->AOR, AOR->CTOR) as I believe it helps to clarify the way different components are affected by the change.

Code changes in Bitcoin ABC

In Bitcoin ABC, several thousand lines of code have been changed from version 0.17.1 to version 0.18.1 (the current version at time of writing). The differences can be viewed here, on github. The vast majority of these changes appear to be various refactorings, code style changes, and so on. The relevant bits of code that deal with the November hard fork activation can be found by searching for "MagneticAnomaly"; the variable magneticanomalyactivationtime sets the time at which the new rules will activate.
The main changes relating to transaction ordering are found in the file src/validation.cpp:
There are other changes as well:


Serial block processing (one thread)

One of the most important steps in validating blocks is updating the unspent transaction outputs (UTXO) set. It is during this process that double spends are detected and invalidated.
The standard way to process a block in bitcoin is to loop through transactions one-by-one, removing spent outputs and then adding new outputs. This straightforward approach requires exact topological order and fails otherwise (therefore it automatically verifies TTOR). In pseudocode:
for tx in transactions: remove_utxos(tx.inputs) add_utxos(tx.outputs) 
Note that modern implementations do not apply these changes immediately, rather, the adds/removes are saved into a commit. After validation is completed, the commit is applied to the UTXO database in batch.
By breaking this into two loops, it becomes possible to update the UTXO set in a way that doesn't care about ordering. This is known as the outputs-then-inputs (OTI) algorithm.
for tx in transactions: add_utxos(tx.outputs) for tx in transactions: remove_utxos(tx.inputs) 
Benchmarks by Jonathan Toomim with Bitcoin ABC, and by myself with ElectrumX, show that the performance penalty of OTI's two loops (as opposed to the one loop version) is negligible.

Concurrent block processing

The UTXO updates actually form a significant fraction of the time needed for block processing. It would be helpful if they could be parallelized.
There are some concurrent algorithms for block validation that require quasi-topological order to function correctly. For example, multiple workers could process the standard loop shown above, starting at the beginning. A worker temporarily pauses if the utxo does not exist yet, since it's possible that another worker will soon create that utxo.
There are issues with such order-sensitive concurrent block processing algorithms:
In contrast, the OTI algorithm's loops are fully parallelizable: the worker threads can operate in an independent manner and touch transactions in any order. Until recently, OTI was thought to be unable to verify TTOR, so one reason to remove TTOR was that it would allow changing to parallel OTI. It turns out however that this is not true: Jonathan Toomim has shown that TTOR enforcement is easily added by recording new UTXOs' indices within-block, and then comparing indices during the remove phase.
In any case, it appears to me that any concurrent validation algorithm would need such additional code to verify that TTOR is being exactly respected; thus for concurrent validation TTOR is a hindrance at best.

Advanced parallel techniques

With Bitcoin Cash blocks scaling to large sizes, it may one day be necessary to scale onto advanced server architectures involving sharding. A lot of discussion has been made over this possibility, but really it is too early to start optimizing for sharding. I would note that at this scale, TTOR is not going to be helpful, and CTOR may or may not lead to performance optimizations.

Block propagation (graphene)

A major bottleneck that exists in Bitcoin Cash today is block propagation. During the stress test, it was noticed that the largest blocks (~20 MB) could take minutes to propagate across the network. This is a serious concern since propagation delays mean increased orphan rates, which in turn complicate the economics and incentives of mining.
'Graphene' is a set reconciliation technique using bloom filters and invertible bloom lookup tables. It drastically reduces the amount of bandwidth required to communicate a block. Unfortunately, the core graphene mechanism does not provide ordering information, and so if many orderings are possible then ordering information needs to be appended. For large blocks, this ordering information makes up the majority of the graphene message.
To reduce the size of ordering information while keeping TTOR, miners could optionally decide to order their transactions in a canonical ordering (Gavin's order, for example) and the graphene protocol could be hard coded so that this kind of special order is transmitted in one byte. This would add a significant technical burden on mining software (to create blocks in such a specific unusual order) as well as graphene (which must detect this order, and be able to reconstruct it). It is not clear to me whether it would be possible to efficiently parallelize sorting algortithms that reconstruct these orderings.
The adoption of CTOR gives an easy solution to all this: there is only one ordering, so no extra ordering information needs to be appended. The ordering is recovered with a comparison sort, which parallelizes better than a topological sort. This should simplify the graphene codebase and it removes the need to start considering supporting various optional ordering encodings.

Reversibility and technical debt

Can the change to CTOR be undone at a later time? Yes and no.
For block validators / block explorers that look over historical blocks, the removal of TTOR will permanently rule out usage of the standard serial processing algorithm. This is not really a problem (aside from the one-time annoyance), since OTI appears to be just as efficient in serial, and it parallelizes well.
For anything that deals with new blocks (like graphene, network protocol, block builders for mining, new block validation), it is not a problem to change the ordering at a later date (to AOR / TTOR or back to CTOR again, or something else). These changes would add no long term technical debt, since they only involve new blocks. For past-block validation it can be retroactively declared that old blocks (older than a few months) have no ordering requirement.

Summary and outlook

Taking a broader view, graphene is not the magic bullet for network propagation. Even with the CTOR-improved graphene, we might not see vastly better performance right away. There is also work needed in the network layer to simply move the messages faster between nodes. In the last stress test, we also saw limitations on mempool performance (tx acceptance and relaying). I hope both of these fronts see optimizations before the next stress test, so that a fresh set of bottlenecks can be revealed.
submitted by markblundeberg to btc [link] [comments]

Emergent Coding FAQ

Background reading
  1. ELI5 with pictures.
  2. Hello World using Emergent Coding
  3. This document treats Emergent coding from a philosophical perspective. It has a good introduction, description of the tech and is followed by two sections on justifications from the perspective of Fred Brooks No Silver Bullet criteria and an industrialization criteria.
  4. Mark Fabbro's presentation from the Bitcoin Cash City Conference which outlines the motivation, basic mechanics, and usage of Bitcoin Cash in reproducing the industrial revolution in the software industry.
  5. Building the Bitcoin Cash City presentation highlighting how the emergent coding group of companies fit into the adoption roadmap of North Queensland.
  6. Forging Chain Metal by Paul Chandler CEO of Aptissio, one of startups in the emergent coding space and which secured a million in seed funding last year.
  7. Bitcoin Cash App Exploration A series of Apps that are some of the first to be built by emergent coding and presented, and in the case of Cashbar, demonstrated at the conference.
  8. A casual Bitcoin Cash interview that touches on emergent coding, tech park, merchant adoption and much more.
How does Emergent Coding prevent developer capture?
A developer's Agent does not know what project they are contributing to and is thus paid for the specific contribution. The developer is controlling the terms of the payment rather than the alternative, an employer with an employment agreement.
Why does Emergent Coding use Bitcoin BCH?
  1. Both emergent coding and Bitcoin BCH are decentralized: As emergent coding is a decentralized development environment consisting of Agents providing respective design services, each contract received by an agent requires a BCH payment. As Agents are hosted by their developer owners which may be residing in one of 150 countries, Bitcoin Cash - an electronic peer-to-peer electronic cash system - is ideal to include a developer regardless of geographic location.
  2. Emergent coding will increase the value of the Bitcoin BCH blockchain: With EC, there are typically many contracts to build an application (Cashbar was designed with 10000 contracts or so). EC adoption will increase the value of the Bitcoin BCH blockchain in line with this influx of quality economic activity.
  3. Emergent coding is being applied to BCH software first: One of the first market verticals being addressed with emergent coding is Bitcoin Cash infrastructure. We are already seeing quality applications created using emergent coding (such as the HULA, Cashbar, PH2, vending, ATMs etc). More apps and tools supporting Bitcoin cash will attract more merchants and business to BCH.
  4. Emergent coding increases productivity: Emergent coding increases developer productivity and reduces duplication compared to other software development methods. Emergent coding can provide BCH devs with an advantage over other coins. A BCH dev productivity advantage will accelerate Bitcoin BCH becoming the first global currency.
  5. Emergent coding produces higher quality binaries: Higher quality software leads to a more reliable network.

1. Who/what is Code Valley? Aptissio? BCH Tech Park? Mining and Server Complex?
Code Valley Corp Pty Ltd is the company founded to commercialize emergent coding technology. Code Valley is incorporated in North Queensland, Australia. See
Aptissio Australia Pty Ltd is a company founded in North Queensland and an early adopter of emergent coding. Aptissio is applying EC to Bitcoin BCH software. See
Townsville Technology Precincts Pty Ltd (TTP) was founded to bring together partners to answer the tender for the Historic North Rail Yard Redevelopment in Townsville, North Queensland. The partners consist of P+I, Conrad Gargett, HF Consulting, and a self-managed superannuation fund(SMSF) with Code Valley Corp Pty Ltd expected to be signed as an anchor tenant. TTP answered a Townsville City Council (TCC) tender with a proposal for a AUD$53m project (stage 1) to turn the yards into a technology park and subsequently won the tender. The plan calls for the bulk of the money is to be raised in the Australian equity markets with the city contributing $28% for remediation of the site and just under 10% from the SMSF. Construction is scheduled to begin in mid 2020 and be competed two years later.
Townsville Mining Pty Ltd was set up to develop a Server Complex in the Kennedy Energy Park in North Queensland. The site has undergone several studies as part of a due diligence process with encouraging results for its competitiveness in terms of real estate, power, cooling and data.
  1. TM are presently in negotiations with the owners of the site and is presently operating under an NDA.
  2. The business model calls for leasing "sectors" to mining companies that wish to mine allowing companies to control their own direction.
  3. Since Emergent Coding uses the BCH rail, TM is seeking to contribute to BCH security with an element of domestic mining.
  4. TM are working with American partners to lease one of the sectors to meet that domestic objective.
  5. The site will also host Emergent Coding Agents and Code Valley and its development partners are expected to lease several of these sectors.
  6. TM hopes to have the site operational within 2 years.
2. What programming language are the "software agents" written in.
Agents are "built" using emergent coding. You select the features you want your Agent to have and send out the contracts. In a few minutes you are in possession of a binary ELF. You run up your ELF on your own machine and it will peer with the emergent coding and Bitcoin Cash networks. Congratulations, your Agent is now ready to accept its first contract.
3. Who controls these "agents" in a software project
You control your own Agents. It is a decentralized development system.
4. What is the software license of these agents. Full EULA here, now.
A license gives you the right to create your own Agents and participate in the decentralized development system. We will publish the EULA when we release the product.
5. What kind of software architecture do these agents have. Daemons Responding to API calls ? Background daemons that make remote connection to listening applications?
Your Agent is a server that requires you to open a couple of ports so as to peer with both EC and BCH networks. If you run a BCH full node you will be familiar with this process. Your Agent will create a "job" for each contract it receives and is designed to operate thousands of jobs simultaneously in various stages of completion. It is your responsibility to manage your Agent and keep it open for business or risk losing market share to another developer capable of designing the same feature in a more reliable manner (or at better cost, less resource usage, faster design time etc.). For example, there is competition at every classification which is one reason emergent coding is on a fast path for improvement.
It is worth reiterating here that Agents are only used in the software design process and do not perform any role in the returned project binary.
6. What is the communication protocol these agents use.
The protocol is proprietary and is part of your license.
7. Are the agents patented? Who can use these agents?
It is up to you if you want to patent your Agent the underlying innovation behind emergent coding is _feasible_ developer specialization. Emergent coding gives you the ability to contribute to a project without revealing your intellectual property thus creating prospects for repeat business; It renders software patents moot.
Who uses your Agents? Your Agents earn you BCH with each design contribution made. It would be wise to have your Agent open for business at all times and encourage everyone to use your design service.
8. Do I need to cooperate with Code Valley company all of the time in order to deploy Emergent Coding on my software projects, or can I do it myself, using documentation?
It is a decentralized system. There is no single point of failure. Code Valley intends to defend the emergent coding ecosystem from abuse and bad actors but that role is not on your critical path.
9. Let's say Electron Cash is an Emergent Coding project. I have found a critical bug in the binary. How do I report this bug, what does Jonald Fyookball need to do, assuming the buggy component is a "shared component" puled from EC "repositories"?
If you built Electron Cash with emergent coding it will have been created by combining several high level wallet features designed into your project by their respective Agents. Obviously behind the scenes there are many more contracts that these Agents will let and so on. For example the Cashbar combines just 16 high level Point-of-Sale features but ultimately results in more than 10,000 contracts in toto. Should one of these 10,000 make a design error, Jonald only sees the high level Agents he contracted. He can easily pinpoint which of these contractors are in breach. Similarly this contractor can easily pinpoint which of its sub-contractors is in breach and so on. The offender that breached their contract wherever in the project they made their contribution, is easily identified. For example, when my truck has a warranty problem, I do not contact the supplier of the faulty big-end bearing, I simply take it back to Mazda who in turn will locate the fault.
Finally "...assuming the buggy component is a 'shared component' puled from EC 'repositories'?" - There are no repositories or "shared component" in emergent coding.
10. What is your licensing/pricing model? Per project? Per developer? Per machine?
Your Agent charges for each design contribution it makes (ie per contract). The exact fee is up to you. The resulting software produced by EC is unencumbered. Code Valley's pricing model consists of a seat license but while we are still determining the exact policy, we feel the "Valley" (where Agents advertise their wares) should charge a small fee to help prevent gaming the catalogue and a transaction fee to provide an income in proportion to operations.
11. What is the basic set of applications I need in order to deploy full Emergent Coding in my software project? What is the function of each application? Daemons, clients, APIs, Frontends, GUIs, Operating systems, Databases, NoSQLs? A lot of details, please.
There's just one. You buy a license and are issued with our product called Pilot. You run Pilot (node) up on your machine and it will peer with the EC and BCH networks. You connect your browser to Pilot typically via localhost and you're in business. You can build software (including special kinds of software like Agents) by simply combining available features. Pilot allows you to specify the desired features and will manage the contracts and decentralized build process. It also gives you access to the "Valley" which is a decentralized advertising site that contains all the "business cards" of each Agent in the community, classified into categories for easy search.
If we are to make a step change in software design, inventing yet another HLL will not cut it. As Fred Brooks puts it, an essential change is needed.
12. How can I trust a binary when I can not see the source?
The Emergent Coding development model is very different to what you are use to. There are ways of arriving at a binary without Source code.
The Agents in emergent coding design their feature into your project without writing code. We can see the features we select but can not demonstrate the source as the design process doesn't use a HLL.
The trust model is also different. The bulk of the testing happens _before_ the project is designed not _after_. Emergent Coding produces a binary with very high integrity and arguably far more testing is done in emergent coding than in incumbent methods you are used to.
In emergent coding, your reputation is built upon the performance of your Agent.
If your Agent produces substandard features, you are simply creating an opportunity for a competitor to increase their market share at your expense.
Here are some points worth noting regarding bad actor Agents:
  1. An Agent is a specialist and in emergent coding is unaware of the project they are contributing to. If you are a bad actor, do you compromise every contract you receive? Some? None?
  2. Your client is relying on the quality of your contribution to maintain their own reputation. Long before any client will trust your contributions, they will have tested you to ensure the quality is at their required level. You have to be at the top of your game in your classification to even win business. This isn't some shmuck pulling your routine from a library.
  3. Each contract to your agent is provisioned. Ie you advertise in advance what collaborations you require to complete your design. There is no opportunity for a "sign a Bitcoin transaction" Agent to be requesting "send an HTTP request" collaborations.
  4. Your Agent never gets to modify code, it makes a design contribution rather than a code contribution. There is no opportunity to inject anything as the mechanism that causes the code to emerge is a higher order complexity of all Agent involvement.
  5. There is near perfect accountability in emergent coding. You are being contracted and paid to do the design. Every project you compromise has an arrow pointed straight at you should it be detected even years later.
Security is a whole other ball game in emergent coding and current rules do not necessarily apply.
13. Every time someone rebuilds their application, do they have to pay over again for all "design contributions"? (Or is the ability to license components at fixed single price for at least a limited period or even perpetually, supported by the construction (agent) process?)
You are paying for the design. Every time you build (or rebuild) an application, you pay the developers involved. They do not know they are "rebuilding". This sounds dire but its costs far less than you think and there are many advantages. Automation is very high with emergent coding so software design is completed for a fraction of the cost of incumbent design methods. You could perhaps rebuild many time before matching incumbent methods. Adding features is hard with incumbent methods "..very few late-stage additions are required before the code base transforms from the familiar to a veritable monster of missed schedules, blown budgets and flawed products" (Brooks Jr 1987) whereas with emergent coding adding a late stage feature requires a rebuild and hence seamless integration. With Emergent Coding, you can add an unlimited number of features without risking the codebase as there isn't one.
The second part of your question incorrectly assumes software is created from licensed components rather than created by paying Agents to design features into your project without any licenses involved.
14. In this construction process, is the vendor of a particular "design contribution" able to charge differential rates per their own choosing? e.g. if I wanted to charge a super-low rate to someone from a 3rd world country versus charging slightly more when someone a global multinational corporation wants to license my feature?
Yes. Developers set the price and policy of their Agent's service. The Valley (where your Agent is presently advertised) presently only supports a simple price policy. The second part of your question incorrectly assumes features are encumbered with licenses. A developer can provide their feature without revealing their intellectual property. A client has the right to reuse a developer's feature in another project but will find it uneconomical to do so.
15. Is "entirely free" a supported option during the contract negotiation for a feature?
Yes. You set the price of your Agent.
16. "There is no single point of failure." Right now, it seems one needs to register, license the construction tech etc. Is that going to change to a model where your company is not necessarily in that loop? If not, don't you think that's a single point of failure?
It is a decentralized development system. Once you have registered you become part of a peer-to-peer system. Code Valley has thought long and hard about its role and has chosen the reddit model. It will set some rules for your participation and will detect or remove bad actors. If, in your view, Code Valley becomes a bad actor, you have control over your Agent, private keys and IP, you can leave the system at any time.
17. What if I can't obtain a license because of some or other jurisdictional problem? Are you allowed to license the technology to anywhere in the world or just where your government allows it?
We are planning to operate in all 150 countries. As ec is peer-to-peer, Code Valley does not need to register as a digital currency exchange or the like. Only those countries banning BCH will miss out (until such times as BCH becomes the first global electronic cash system).
For example the Cashbar combines just 16 high level Point-of-Sale features but ultimately results in more than 10,000 contracts in toto.
It seems already a reasonably complex application, so well done in having that as a demo.
Thank you.
19. I asked someone else a question about how it would be possible to verify whether an application (let's say one received a binary executable) has been built with your system of emergent consensus. Is this possible?
Yes of course. If you used ec to build an application, you can sign it and claim anything you like. Your client knows it came from you because of your signature. The design contributions making up the application are not signed but surprisingly there is still perfect accountability (see below).
20. I know it is possible to identify for example all source files and other metadata (like build environment) that went into constructing a binary, by storing this data inside an executable.
All metadata emergent coding is now stored offline. When your Agent completes a job, you have a log of the design agreements you made with your peers etc., as part of the log. If you are challenged at a later date for breaching a design contract, you can pull your logs to see what decisions you made, what sub-contracts were let etc. As every Agent has their own logs, the community as a whole has a completely trustless log of each project undertaken.
21. Is this being done with EC build products and would it allow the recipient to validate that what they've been provided has been built only using "design contributions" cryptographically signed by their providers and nothing else (i.e. no code that somehow crept in that isn't covered by the contracting process)?
The emergent coding trust model is very effective and has been proven in other industries. Remember, your Agent creates a feature in my project by actually combining smaller features contracted from other Agents, thus your reputation is linked to that of your suppliers. If Bosch makes a faulty relay in my Ford, I blame Ford for a faulty car not Bosch when my headlights don't work. Similarly, you must choose and vet your sub-contractors to the level of quality that you yourself want to project. Once these relationships are set up, it becomes virtually impossible for a bad actor to participate in the system for long or even from the get go.
22. A look at code generated and a surprising answer to why is every intermediate variable spilled?
Thanks to u/R_Sholes, this snippet from the actual code for: number = number * 10 + digitgenerated as a part of: sub read/integeboolean($, 0, 100) -> guess
; copy global to local temp variable 0x004032f2 movabs r15, global.current_digit 0x004032fc mov r15, qword [r15] 0x004032ff mov rax, qword [r15] 0x00403302 movabs rdi, local.digit 0x0040330c mov qword [rdi], rax ; copy global to local temp variable 0x0040330f movabs r15, global.guess 0x00403319 mov r15, qword [r15] 0x0040331c mov rax, qword [r15] 0x0040331f movabs rdi, local.num 0x00403329 mov qword [rdi], rax ; multiply local variable by constant, uses new temp variable for output 0x0040332c movabs r15, local.num 0x00403336 mov rax, qword [r15] 0x00403339 movabs rbx, 10 0x00403343 mul rbx 0x00403346 movabs rdi, local.num_times_10 0x00403350 mov qword [rdi], rax ; add local variables, uses yet another new temp variable for output 0x00403353 movabs r15, local.num_times_10 0x0040335d mov rax, qword [r15] 0x00403360 movabs r15, local.digit 0x0040336a mov rbx, qword [r15] 0x0040336d add rax, rbx 0x00403370 movabs rdi, local.num_times_10_plus_digit 0x0040337a mov qword [rdi], rax ; copy local temp variable back to global 0x0040337d movabs r15, local.num_times_10_plus_digit 0x00403387 mov rax, qword [r15] 0x0040338a movabs r15, global.guess 0x00403394 mov rdi, qword [r15] 0x00403397 mov qword [rdi], rax For comparison, an equivalent snippet in C compiled by clang without optimizations gives this output: imul rax, qword ptr [guess], 10 add rax, qword ptr [digit] mov qword ptr [guess], rax 
Collaborations at the byte layer of Agents result in designs that spill every intermediate variable.
Firstly, why this is so?
Agents from this early version only support one catch-all variable design when collaborating. Similar to a compiler when all registers contain variables, the compiler must make a decision to spill a register temporarily to main memory. The compiler would still work if it spilled every variable to main memory but would produce code that would be, as above, hopelessly inefficient.
However, by only supporting the catch-all portion of the protocol, the code valley designers were able to design, build and deploy these agents faster because an Agent needs fewer predicates in order to participate in these simpler collaborations.
The protocol involved however, can have many "Policies" besides the catch-all default policy (Agents can collaborate over variables designed to be on the stack, or, as is common for intermediate variables, designed to use a CPU register, and so forth).
This example highlights one of the very exciting aspects of emergent coding. If we now add a handful of additional predicates to a handful of these byte layer agents, henceforth ALL project binaries will be 10x smaller and 10x faster.
Finally, there can be many Agents competing for market share at each of classification. If these "gumby" agents do not improve, you can create a "smarter" competitor (ie with more predicates) and win business away from them. Candy from a baby. Competition means the smartest agents bubble to the top of every classification and puts the entire emergent coding platform on a fast path for improvement. Contrast this with incumbent libraries which does not have a financial incentive to improve. Just wait until you get to see our production system.
23. How hard can an ADD Agent be?
Typically an Agent's feature is created by combining smaller features from other Agents. The smallest features are so devoid of context and complexity they can be rendered by designing a handful of bytes in the project binary. Below is a description of one of these "byte" layer Agents to give you an idea how they work.
An "Addition" Agent creates the feature of "adding two numbers" in your project (This is an actual Agent). That is, it contributes to the project design a feature such that when the project binary is delivered, there will be an addition instruction somewhere in it that was designed by the contract that was let to this Agent.
If you were this Agent, for each contract you received, you would need to collaborate with peers in the project to resolve vital requirements before you can proceed to design your binary "instruction".
Each paid contract your Agent receives will need to participate in at least 4 collaborations within the design project. These are:
  1. Input A collaboration
  2. Input B collaboration
  3. Result collaboration
  4. Construction site collaboration
You can see from the collaborations involved how your Agent can determine the precise details needed to design its instruction. As part of the contract, the Addition Agent will be provisioned with contact details so it can join these collaborations. Your Agent must collaborate with other stakeholders in each collaboration to resolve that requirement. In this case, how a variable will be treated. The stakeholders use a protocol to arrive at an Agreement and share the terms of the agreement. For example, the stakeholders of collaboration “Input A” may agree to treat the variable as an signed 64bit integer, resolve to locate it at location 0x4fff2, or alternatively agree that the RBX register should be used, or agree to use one of the many other ways a variable can be represented. Once each collaboration has reached an agreement and the terms of that agreement distributed, your Agent can begin to design the binary instruction. The construction site collaboration is where you will exactly place your binary bytes.
The construction site protocol is detailed in the whitepaper and is some of the magic that allows the decentralized development system to deliver the project binary. The protocol consists of 3 steps,
  1. You request space in the project binary be reserved.
  2. You are notified of the physical address of your requested space.
  3. You delver the the binary bytes you designed to fill the reserved space.
Once the bytes are returned your Agent can remove the job from its work schedule. Job done, payment received, another happy customer with a shiny ADD instruction designed into their project binary.
  1. Observe how it is impossible for this ADD Agent to install a backdoor undetected by the client.
  2. Observe how the Agent isn’t linking a module, or using a HLL to express the binary instruction.
  3. Observe how with just a handful of predicates you have a working "Addition" Agent capable of designing the Addition Feature into a project with a wide range of collaboration agreements.
  4. Observe how this Agent could conceivably not even design-in an ADD instruction if one of the design time collaboration agreements was a literal "1" (It would design in an increment instruction). There is even a case where this Agent may not deliver any binary to build its feature into your project!
24. How does EC arrive at a project binary without writing source code?
Devs using EC combine features to create solutions. They don't write code. EC devs contract Agents which design the desired features into their project for a fee. Emergent coding uses a domain specific contracting language (called pilot) to describe the necessary contracts. Pilot is not a general purpose language. As agents create their features by similarly combining smaller features contracted from peer, your desired features may inadvertently result in thousands of contracts. As it is agents all the way down, there is no source code to create the project binary.
Traditional: Software requirements -> write code -> compile -> project binary (ELF).
Emergent coding: Select desired features -> contract agents -> project binary (ELF).
Agents themselves are created the same way - specify the features you want your agent to have, contract the necessary agents for those features and viola - agent project binary (ELF).
25. How does the actual binary code that agents deliver to each other is written?
An agent never touches code. With emergent coding, agents contribute features to a project, and leave the project binary to emerge as the higher-order complexity of their collective effort. Typically, agents “contribute” their feature by causing smaller features to be contributed by peers, who in turn, do likewise. By mapping features to smaller features delivered by these peers, agents ensure their feature is delivered to the project without themselves making a direct code contribution.
Peer connections established by these mappings serve to both incrementally extend a temporary project “scaffold” and defer the need to render a feature as a code contribution. At the periphery of the scaffold, features are so simple they can be rendered as a binary fragment with these binary fragments using the information embodied by the scaffold to guide the concatenation back along the scaffold to emerge as the project binary - hence the term Emergent Coding.
Note the scaffold forms a temporary tree-like structure which allows virtually all the project design contracts to be completed in parallel. The scaffold also automatically limits an agent's scope to precisely the resources and site for their feature. It is why it is virtually impossible for an agent to install a "back door" or other malicious code into the project binary.
submitted by nlovisa to EmergentCoding [link] [comments]

The Bitconnect Codebase Python Requests Tutorial - Bitcoin Price API Coding a Simple Bitcoin Paywall in Under 10 Minutes - YouTube Bitcoin scan database 2020

Coinbase is a secure platform that makes it easy to buy, sell, and store cryptocurrency like Bitcoin, Ethereum, and more. Based in the USA, Coinbase is available in over 30 countries worldwide. With Bitcoin, Wright claims he owns all the rights to the original codebase. “As the sole creator of Bitcoin, I own full rights to the Bitcoin registry,” Wright asserted. “People can fork my ... Date Abuse Type Abuser Description; Aug 24, 2020 : blackmail scam [email protected] Héllo! I'm a programmér who crackéd your émail account and dévicé about half yéar ago. After adding all that information to the database, Bob’s server displays a “bitcoin:” URI for Charlie to click to pay. Charlie clicks on the “bitcoin:” URI in his browser. His browser’s URI handler sends the URI to his wallet program. The wallet is aware of the Payment Protocol, so it parses the “r” parameter and sends an HTTP GET to that URL looking for a PaymentRequest ... Bitcoin Abuse Database. Report history for 1NZz572KoTSJgTNAEZsZw1f2Gtd9cVPQZj. Address found in database: Address: 1NZz572KoTSJgTNAEZsZw1f2Gtd9cVPQZj: Report Count: 14: Latest Report: Sat, 04 Jul 20 06:59:52 +0000 (3 months ago) View address on . If you have additional information about this address, please file a report. Reports: Date Abuse Type Abuser Description; Jul 4, 2020

[index] [542] [41782] [33933] [19899] [46145] [8596] [1246] [12342] [38436] [38595]

"The Real Bitcoin"

That markets choose to identify a particular network with a particular ticker symbol does not make that network “The Real Bitcoin.” That a particular network... Today, we dig deep into the code of Bitconnect. From the coin to the wallet, to the nodes and the network, we look at the what powers Bitconnect behind the scenes. Bitconnect is the newest way to ... bitcoin private key database download, bitcoin private key database 2019, bitcoin private key database search, bitcoin private key database with balance, bitcoin private key database with balance ... Pieter Wuille is one of the most prolific and respected Bitcoin developers. He has the 3rd most commits to the Bitcoin codebase and is the person who propose... Bitcoin and cryptocurrency mining explained with the Byzantine Generals Problem. We use it to explain the essence of cryptocurrency mining. https://www.udemy...