IBM created both Bitcoin and Ethereum with Nick Szabo (& I’m pumped)

 

I don’t even believe that dates even matter much to me anymore. When came where and why or how. The reason has a lot to do with understanding someone and how they operate. If they leave enough literature out there for me to read, as a research graduate, I tend to figure the gist of things out. This is my first experience with open source projects, but I am so glad I don’t listen to anyone but myself when it comes to financial advice. The reasons here apply as follows:

1. I can figure out someones end game or at least their honest intentions pretty quickly in person, but I have developed the ability to do it from hard facts gathered from all over the internet. I’m proud of that.
2. Making something abstract only seems to attract me further towards it and I don’t know why. I go with my intuition and follow up by studying the facts of the matter.

I am honestly beyond excited for the future being built. First off, I will just let you know the bulletpoints of what I know:

 

1. Nick Szabo came up with the idea for Smart Contracts, but he also played his part in launching what would become both Bitcoin and Ethereum in the present day. IBM likely worked with Szabo in the 1990’s before launching their first POW (Hashcash) and RPOW (by Hal Finney) in the early parts of the millennium.
2. “Mark S. Miller” who I also have seen called Mark Metson on the Devcoin Github, wrote a paper in 2000 that describes a lot of things he has done in his time as “markm” on bitcointalk.org. He gives special thanks to Nick Szabo at the end of the paper I am going to review here today, Capability based Financial Instruments.
3. Nick Szabo’s Theory of Collectibles and the Devtome Wiki have huge parallels in their message. Covering things like shell money, scrip, and value being built over time. Finney explains in his World of RPOW website how it would take a long time for RPOW to become valuable and mentions things about servers crashing, but still coming back online. He gives a classic inform and disinform approach to let you decide by evaluating for yourself — that’s a huge part of “Game Theory” and it’s also described by markm in the Capability based Financial Instruments paper from 2000.
4. RPOW incorporated Hashcash and Hashcash became Bitcoin’s preferred POW — yet Hal Finney was the first “dev” that ever debugged the software for Satoshi. The interesting part to me is that it seemed less like Satoshi actually existed, and even less like Hal existed as I read more of their interactions. They had sourcefourge posts where they would post a day early about a problem they had when I saw the data on the logs came a day later. The genesis block is obscured by not knowing if it did happen in 2008 by that one debug log, but if it did it seems like it would’ve been Hal. The genesis block connects to the prev hash which is an empty string of zeros representing the epoch.
5. Hal Finney used IBM 4758 co-processing units for RPOW which to me represented something that will “co-process” dual chains, a so called alternate bitcoin chain that is clearly Devcoin after all the data I’ve show in: minting bitcoins and having script to call back the funds most likely with similar RSA-4096 keys like these. The debug log I found for Devcoin shows it exists on blk00000.dat and the first instance of a description for that is in Bitcoin ABE (more on that later). Just know that 4096*4096 is equal to 0x1000000 which the debug from Devcoin genesis says it was “pre-allocating” and somehow Devcoin already had 32.000022 in log-base2 POW. The 0x1000000 is important because it’s decimal equivalent to 16777216 ( 2²⁴). We are talking about value in bits and that explains why everything allocated up to Devcoin genesis being debugged makes up what you can format into all 16,777,216 (R, G, B) colors — which I discuss later.
6. Devcoin exists in a token/coin state. It’s pegged to a recyclable type function in that it has POW from being a coin yet it can transform into tokens. It has created its own alternate blockchain and it even tokenized that. The reason why record doesn’t exist many places for its block 0 is tied to Bitcoin ABE protocol. Once something is hardcoded to the chain it doesn’t need to exist there. Currently Devcoin mints a lot of Bitcoin’s raw blocks. That was something ABE also implemented by not getting tx’s from raw transactions, but from the block itself. I will discuss that more as well. Why it ties back to Devcoin, how ABE went to Ethereum, how ABC’s Copernicus is going to help us come back, and why Ethereum Foundation gave 15,000 to ETC “OTC” — or even had ETC to begin with. It’s very connected. Even Satoshi’s Vision should really bring about the actual vision. Everything interesting with POW that I discussed in my last two entries happened in November in various years. Even early blocks were received elsewhere showing they weren’t confirmed for 5 years (2009-Nov. 2014). That is called abstraction and game theory and my review of markm’s paper will cover that process.
7. Devcoin and ABE share a start (the blk.dat file is 00000 to begin the filing for ABE) and I am sure ABE has configured as such while hardcoding and removing different genesis blocks and information that was set since 2011. ABE is under the GNU license like Ethereum and it even has a coin called “Bitlieu” which was changed to be measured with 6 decimals. It could just be a set of blocks that were to be written later with Devcoin’s own data.
8. Because Nick Szabo and markm are connected through “E” which is money, I tied that to Satoshi who credited Hal with E-money in Duality and knew that wasn’t quite true. I knew of B-Money and Nick Szabo made smart contracts, but then I found the link for markm’s website where he goes by Mark S. Miller and has all of his previous published work that you can find on Satoshi Nakamoto Institute’s research section. There he credits Szabo for smart contracts proving a tie again and explains a money unit called “E” which is linked here. That link provides what looks a raw ether script for a smart contract.
9. DevCoin’s use as a 1.00000000 measure for everything converting through decimal to tonal. It is an exact conversion at the moment in current sValue around 655360 to Bitcoin. Because Devcoin is only changed two decimal places we need to divide the price by 10 to get one true Tonal Bitcoin, worth 65536 satoshis. If DVC is worth 10*65536 when adjusted to the current market it explains why they chose 65536 as the measure for 1 TBC — it is a divisor for 16777216. The value of the future is in both time, bits, and processing (colors). Proof of work is tied in more ways than one would think. And remember, the 4096 RSA keys from RPOW can unwind the whole formula before Web 3.0 arrives. The smart contract executes with the right keys and we see the grand plan unfold. However because of the Y2K38 problem, you will see many things going forward in Python 3, which fixes the integer overflow problem and happens to be what the Web 3.0 is building on. You can’t build a financial store of value only to have it disappear in a Y2K38 event.
10. Devcoin’s value is almost approximate at Galactic Milieu, but I also want to tie mark to IBM with all of the overlaps between himself, his paper I am trying to get to explaining eventually, and through Devcoin’s connection to RPOW, POW, Bitcoin, and use of IBM products. Finney used the IBM 4758 and Bitcoin ABE uses IBM DB 2 databases and lambda calculus in it’s code. It also mentions use of switching to Python 3. Markm’s paper in 2000 explains: “E blends the lambda calculus, capability security, and modern cryptography.”
11. The paper also discusses using E for the stock market amongst other assets. I am sure if IBM wanted to start an online form of currency as well as put up their own stock (which would be involved in making machines for the operation), they could find others at the Linux Foundation to get involved too — and then some. The format “pluribusunum” from Devcoin’s receiver files is in the 2000 paper too, as “E pluribusunum” and perhaps that’s because the uniting of worlds through Devcoin, RPOW, IBM, and a dual state is the truth. Also if I was wrong, consider this. Who would keep rates going on a “dead coin” and coins that have never been heard of (explained yesterday they are OTC investments)? I’m talking about the Galactic Milieu (by markm). Who would do that? And its so detailed if you can find your way to the other monthly updates. Takes some good computing and record keeping. The Galactic Milieu is Bitcoin ABE, Devcoin’s debugging, Finney, POW and RPOW, Nick Szabo, MarkM, Adam Back, Blockstream, Bitcoin Core devs like Luke Jr., and leads back to IBM.
12. This link explains why Devcoin has the WWA1961 reference in its repo, which explains why MOAC has a reference decoded to the ARPANET1969 at its block 0 at the epoch it shares with Ethereum Classic. All of it is connected through Cloudflare as well via Block Explorer. Not to mention by method of OTC investment Ethereum just set back its own block 0 to the epoch as well — joining Ethereum Classic. I have no doubts DARPA money in $USD is an asset that is invested in the entire Bitcoin/Ethereum ecosystem. IBM is partnered with Stellar. No joke that’s the next distributed ledger and also why markm issues “assets” in DVC and other coins on the Galactic Milieu through “Horizon” and “Stellar”(you should buy some if you haven’t). Devcoin has a large bounty for a Rocket at devcoin.org. It makes plenty of sense.
13. If you don’t believe me, try to explain why Devcoin’s early block explorers were ported to the same place as Bitcoin ABE’s IBM Database 2 (2750). Also, ABE probably uses the same “DataStrore” file as RPOW. But you can find that yourself.
14. Cupertino with an “abstract” company could mean this includes Apple from the start.

Capability-based Financial Instruments: “E”

I’d like to get out of the way the fact that this is “E” and uses smart contracts. Here’s what sample code for “E” as money looks like:

It also looks like escrow does it not? You will recall that DevCoin had its own escrow service early on as I explained that is the process by which it achieves embedded value through Theory of Collectibles, by Nick Szabo. Then I explained today how ABE was tied to Devcoin and Ethereum via genesis blocks even though Devcoin had it’s block hardcoded and stored in a “DataStore” which is the same name Hal Finney used to describe the file in RPOW. Well, in this DataStore, on a shared port 2750, that both Devcoin and ABE have used is not only an updated RPOW on an “IBM DB 2” machine, but also what escrow from 2000’s “E” Money looks like in Python today:

 

The paper states the three types of things that encompass Bitcoin and its derivatives today in the year 2000:

objects have been strong on abstraction and composition,

operating systems have been strong on providing a shared platform in which disparate processes can interact without being able to damage one another, even if they contain malicious code, and

 

financial cryptography has been strong on cooperative protocols allowing mutually suspicious parties to trade a diversity of rights in the absence of a mutually-trusted platform.

This is much of the way Bitcoin works today. It’s about to all become interconnected through Devcoin’s connection to the timechain (using RPOW). Even in Duality, Satoshi writes how RSA was too large to work at the time:

It’s also just a hint/abstraction at what really happened by delaying “RPOW” but still if you read it — you might have it all click and make a great investment. Markm explains the problem in 2000:

Unfortunately, each has been weak in the areas where the other two are strong. By bridging the intuitions of these communities, we can engineer systems with the strengths of all three. The bridge described in this paper is based on a joint appreciation, across all three communities, of a common abstraction, the Granovetter Diagram.

The solution ultimately came in Math, Cryptography, and C++ according to Satoshi in Duality. However I have described here how it goes beyond that. Still, lets take a look at the diagram markm mentions:

In 2000, these were the objectives for the people who make crypto work to this very day:

I will get to each of these areas, but below the six perspectives of this “abstraction” the mission is announced:

We are building the E system [11] to unify these perspectives. E is a simple, secure, distributed, pure-object, persistent programming language. E blends the lambda calculus, capability security, and modern cryptography. In integrating these diverse features, E brings the diverse virtues of the Granovetter Operator to life.

First lets go to the use of lambda calculus and just tied Bitcoin ABE to both Devcoin and Ethereum right now:

Also I’d like to point out the lambda calculus is used to start page 200, which is for a connection to BTC block 200. Here is the actual BTC Block 200 transaction where ABE has a python file ready to go:

Check me if you’d like: 2b1f06c2401d3b49a33c3f5ad5864c0bc70044c4068f9174546f3cfc1887d5ba

The process of starting different coins, chains, or marking a future checkpoint to come back to works like this. The eventual order of the universe is playing out in the many ways I have described in previous articles. Make a branch point, start a new block, and use hardcoding on Devcoin’s blk00000.dat file before putting it in a database called “IBM DB 2″ at the same port 2750 that Devcoin’s early explorer ran off :

I am sure this port was used locally many places. However, the goal is to run Global like Devcoin already does at port 52333. When everything does it will be when IBM and all who cooperated in this abstract project have in mind. It’s amazing that ABE carried out the same AuxPow that Devcoin is the parent of as well, but why wouldn’t it. In the end everything is together as one. It had to be consistent as it all was initially constructed.

The same database is carefully filed away/hardcoded:

Bitcoin ABE last hardcoded the pre-alpha and January 3, 2009 Block 0’s which are written to blk0001.dat together as I wrote about the last two articles:

Back to 2000, here is the Six Objectives explained in the paper:

Objects. The Granovetter Diagram shows the computation step fundamental to all object computation: the “message send” (in Smalltalk terminology) or the “virtual member function call” (in C++ terminology). Alice, Bob, and Carol are three objects. In the initial conditions, Alice holds a reference to (points at, has access to) Bob and Carol. Dynamically, we see that Alice is sending a foo message to (calling the foo member function of) Bob, in which a parameter of the message (call) is a copy of Alice’s reference (pointer, access) to Carol. For conciseness, we will refer to this computation step as the Granovetter Operator. Object-oriented message passing, along with encapsulation and polymorphism, enables modular programming. By designing the interfaces between modules on a need-to-know basis, we satisfy the principle of information hiding [28] that is the basis of much important software engineering theory and practice.

This is exactly what has played out today, they even pegged C++ as the language to begin from back in 2000. They keep copies of messages and use others as a pointer (like witnesses). The interfaces are only what you need to know, meaning nobody is going to go right out and say anything like I do at any point. This is to keep things secure and as the software is open-sourced they aren’t going to give away any information directly. It’s abstract and up for you to figure out. I want to define abstraction before moving forward:

Which is exactly what this first objective just said. This is how crypto is developed and will run in the future as a seamless network. You might wonder if IBM is behind “Techopedia” with a definition so identical. There’s more:

The encapsulation and polymorphism concept is word for word in the first objective quoted above. For inheritance, I will quote Nick Szabo’s Theory of Collectibles:

Kin also benefited from timely and peaceful gifts of wealth by inheritance. The major human life events that modern cultures segregate from the world of trade benefited no less than trade, and sometimes more so, from techniques that lowered transaction costs. None of these techniques was more effective, important, or early than primitive money — collectibles.

Now lets go a step further and intertwine Szabo’s description of shell currency (token currency) with others:

The American language of shell money became a quaint holdover — “a hundred clams” became “a hundred dollars”. “Shelling out” came to mean paying in coins or bills, and eventually by check or credit card.[D94] Little did we know that we had touched the very origins of our species.

Also add to the above with the mention of scrip as token money from Devtome.com:

Token currency is issued by private issuers and communities and has been used centuries. It is used more often in depressions when there is a lack of debt money.Token currencies include the Colonial Scrip, Time Bank, Christiania Coin, Ithaca Hours, and Worgl Schillings.

I covered an unknown named Andrew Dunstan two articles back because he started a project for a widely used PostGreSQL database that would be great to use for a decentralized economy. ABE has PostgreSQL. I also mentioned Andrew Dunstan named his database Build Farm and how that was on the genesis block for iXcoin but missing a timestamp with a quote by Stephen Molyneux — “to see the farm is to leave it” and that’s all tied in with the fact that Andrew Dunstant has attended Sharding Conferences with a guy named Satoshi N.! But I think that the two quotes of token money above really seals the deal:

Andrew mentions Bitcoins in addition to all of the forms of “collectibles” Szabo wrote about in his theory but would you just look at the color of those beads?

Because color, is not only the final block being worked up to/back to at 0x1000000:

Might as well point out that Luke Dash Jr. made the tonal conversion that will be used for the rates markm provides on Galactic Milieu to see what a base price will be through Devcoin, for the future of “E” as well as how he implemented it all since with Devcoin and Bitcoin, etc… Luke’s client that runs tonal numbers is Bitcoin Knots (see above markm uses the knot). Markm also lists assets on this website:

http://makemoney.knotwork.com/horizon/assets/hzgrow/

http://makemoney.knotwork.com/stellar/

Where you can find assets listed on both Horizon and Stellar. The goal is for things to look simple and ABSTRACT.

My last two articles cover Andrew Dunstan and the fact markm’s Galactic Milieu is actually a vehicle for combining money to be made in open source coding, opportunity for all to figure it out like me, as well as OTC institutional grade investors. Read them both.

You can read about Andrew Dunstan on the bottom of this article:

BACK TO THE 2000 PAPER THAT IS AT THE BASE OF IT ALL:

Objective 2 is security, I will just quote it:

Capability Security. The Granovetter Operator becomes a security primitive given the following constraint: If Bob does not already have a reference to Carol, Bob can only come to have a reference to Carol if a third party, such as Alice, • already has a reference to Carol, and • already has a reference to Bob, and • voluntarily decides to share with Bob her reference to Carol.

Objective 3 is Cryptographic Protocol

Imagine now that Alice, Bob, and Carol are objects residing on three separate machines on a computer network. Distributed object systems, such as CORBA [5] and RMI [42], provide for the diagrammed message send to proceed over the network, while preserving the core semantics of the object computation model. However, these are cooperative protocols, in that they rely on the assumption that the machines involved are correctly cooperating. By contrast, a cryptographic protocol implementing the Granovetter Operator must also preserve the semantics of the capability model, including the prohibitions, in the presence of mutually suspicious objects residing on mutually suspicious machines. We briefly explain Pluribus, E’s cryptographic capability protocol, turning E into a securely distributed language. In section 4.4 we examine how the money example (from section 3.4) transparently distributes by showing how Pluribus automatically maps the pieces of the example to stock cryptographic-protocol elements.

This is IMPORTANT to understand. This is why Devcoin has “receiver files”.. the address which they disburse “shares”…. These are tied to the value of all the assets I linked to on Galactic Milieu that he’s already listed on STELLAR and Horizon… Take a look:

First of all, I have explained how this is all tied back to DARPA and the US Dollars/IBM collaboration that went into the making of the arpanet. I can’t explain again my hands are tired. Please find that article. Also there are the lists right there for all of the investors in this project as well as a way to send money correctly back through all checkpoints. Most of all, it’s all pre-calculated. That’s how easy of a call it is to invest in these coins right now from v1 merge mining — especially Devcoin, “ETH”, “E”…

Objective 4 Public Key Infrastructure

Some PKIs, like SPKI (the Simple Public Key Infrastructure [13]), interpret digital certificates primarily as statements authorizing the players to perform various actions on various resources. In the Granovetter Diagram, the message arrow foo can be seen as such a certificate, signed by Alice, stating that Bob has the authority to perform the action represented by Carol. This certificate is meaningful if and only if there is a similar certificate granting Alice this right, and so on, back to the creator/owner of Carol. Should Bob choose to exercise this authority, he would present the certificate-chain (or its logical equivalent) as proof that he has received this authorization. The enforceable subset of SPKI can be seen as an off-line, auditable, heavyweight, non-confinable, semi-capability system, with interesting contrasts to E’s on-line, repudiatable-by-default, lightweight, confinable, full-capability system.

Ready for another bomb, this is where I tie this to Hal Finney, RPOW, and IBM > all the way back to markm and Devcoin/Merge Mining. He suggested SPKI to Hal Finney in 2001:

There’s also Adam Back’s POW. Hashcash is adopted into RPOW, just as inspired by BitGold (Nick Szabo) and embedded value. I’ve written much about that the last three entries. However, this is about markm being the glue in all this through Devcoin but first from “E”.

Adam Back stopped upstream Hashcash merging indicating his newly released shell files 1.0.0.sh and 0.01.sh (which match the first two genesis block releases) — were marked for “pre-release” on November 14, 2016. The interesting part is he makes no mention of uploading the files and they are still market “old” for some reason even though the bar above says they are from that day.

Devcoin is already good to go. No need for fancy updates, thats part of abstraction. The “simple bitcoin” would move forward as the pre-release with POW and 1.0.0.sh to perform (as described in Back’s update): Unset TZ (which works well with all the python upgrades and transition from UNIX timestamps) & “FASTMINT_LIBRARY” …

This Hashcash POW upgrades are to bring up the maxcoin supply to its intended total faster than we all were told. That’s because you could’ve found the truth and verified it yourself. “Simple Bitcoin” matches front end type script from Devcoin’s early days and uses Hashcash upgraded, front end-POW on finalizing Bitcoin POW (Simple Bitcoin repo here). I’m willing to bet November will be another year of change, but a flipping over of the universe nobody expects. The fundamentals are all there.

Objective 5 Game Rules

During a player’s turn in a board game, the state of the board constrains what moves that player may make. From these possible moves, the player chooses a particular move, which changes the board and thereby alters the moves then available to the other players. Recall the three conditions needed for Bob to receive a reference to Carol from Alice. The first two conditions are constraints on the possible moves available to Alice (and so correspond to mandatory security). The third condition is that Alice must choose to make this move (and so corresponds to discretionary security). If Alice actually does choose to make this move, she thereby changes the moves available to Bob — afterwards Bob may both send messages to Carol and send messages to yet other parties introducing Carol to them, whereas previously he could not.

Okay this is about state confining everyone to the way things are now. I can’t send Devcoin to Ethereum yet. However, there are scripts I covered out there that will allow me to receive escrow value as a Devcoin holder on Bitcoin. I showed how some show a little information on Blockchain.com, with more updated information usually at Blockcypher, including updated dates of confirmation years from when they were relayed first. That’s two moves on that contract script to send money escrowed from Devcoin raw blocks, to Bitcoin raw transactions, and back to Devcoin. Alice is the one who must let go and sign off on the escrow. If she (say, Craig Wright tries to hijack core as a “bad guy” in this game)but all the hash power in trying fork the chain wakes up Bob (or an RPOW IBM 4758 with power problems) wakes up and uses it to make a ton of executions on scripts allowing a completely dual-state. Yeah, probably gonna happen. Finney’s code says his co-processors need power and guess who will try to use power in a fake attempt to win the game? Craight Wright, Roger Ver — Idk (he’s just an actor in it even if he’s involved). I don’t care I’m just taking you through the Game Theory. It still makes me wonder how so many people believe in one Satoshi and all the anarchy crap.

Attempts to formalize the semantics of computation, including secure computation, have failed to capture the core intuitions of computer security practitioners. Fundamental to these intuitions is the notion of mutually suspicious, separately interested agents, interacting within a framework of rules, under constraints of partial knowledge, each in order to pursue their own interests. The formal tools for capturing such intuitions are to be found in non-zero-sum, partial-information game theory [33]. The Granovetter Diagram expresses the core game-rule governing secure capability based distributed multi-agent computation, viewed as a vast multi-player game. We have yet to exploit this perspective in order to apply game theory to computation in this manner, but we hope this explanation may point the way. We do not explore the game perspective further in this paper.

This is just indicating the purpose of merge mining was to abstract Bitcoin. It abstracted Ethereum, everything. I only picked up on it after months of research. There’s witnesses in script embedded in merge mined chains. You can see how they are listed on Horizon already in the link I gave earlier (I0C, IXC, DVC, etc).

Objective 6 Financial Bearer Instruments

If Carol provides a useful service, then the ability to send messages to Carol may be a useful right. Perhaps Carol answers questions from a store of knowledge that she alone is privy to. Perhaps she can affect some aspect of the external world, such as pixels on a display or the cash dispenser of an automated teller machine. Any secure system of electronic rights must solve at least three problems:

• How to represent who currently has what rights.

• How to enable rights holders to exercise those rights they have, and no more.

• How to enable rights holders to securely transfer these rights. The static reference relationships among objects exactly represent who currently has what rights. Since a right is exercised by sending a message to an object that embodies the right, such as Carol, the rule that you can send a message to any object you have a reference to, but no others, provides for the exercise of those rights you have, and no others. Finally, the transition shown on the Granovetter Diagram is both the secure transfer to Bob of the right to pass messages to Carol, as well as the exercise, by Alice, of whatever right Bob may represent.

That’s the last step. So again, I would invest in the Galactic Milieu heavily.

Finally, lets look at E Pluribusunum in action from “E Money”:

I am telling you its gonna be a much better day for Devcoin than not. For reasons proven here. I recommend reading about Copernicus in my previous article:

Nicolaus Copernicus was a Renaissance-era mathematician and astronomer who formulated a model of the universe that placed the Sun rather than the Earth at the center of the universe, likely independently of Aristarchus of Samos, who had formulated such a model some eighteen centuries earlier.

That is a Bitcoin ABC update that has a lot of “go” language to funnel money in a Pluribus fashion back to Devcoin. It’s all in script and the languages being programmed elsewhere. ABC, ABE, the Ethereum Foundation donation to ETC, ETC’s part on the Epoch, all the “hacks” in this multiplayer game — it all goes back to DevCoin.

I may update later but that’s enough for now.