Kindle Notes & Highlights
by
Siraj Raval
Read between
April 27 - April 30, 2018
Kerala will pull the merkleDAG hash from our own nodeID using the IPNS resolving strategy. If there is a name, Kerala will get the DAG associated with the name by resolving it. The DAG is an acyclic directed graph, so every time a hash is added to it, it points backward in time to all previous hashes. Does that mean a user’s identity is constantly changing? No — that’s what’s great about IPNS. Kerala utilizes both IPNS and IPFS to work seamlessly together. It will associate the HEAD node of a particular DAG with a particular peerID, republishing to IPNS as necessary when new data is added.
Peers are identified by their default peerID generated by IPFS. Let’s examine how we got them in app.go.
We pull all the peers from the peerstore; internally, this is the IPFS swarm peers command. Next, we create an array the length of peers and iterate through it.
When the transaction has been completed, the new address will have all X shares of dapp coins you’ve just created, as demonstrated in Figure 3-4. After you’ve finished that step, you should see your new currency on your wallet home page, next to your Bitcoin amount. Congrats! You now own all of the assets you’ve just created. Think of them as shares in your dapp startup. You can give them away to whomever you want, and as the valuation of your startup increases, so will the valuation of your shares. No more waiting for IPOs to become a public company.
Pay(fee string, from_address string, to_address string, amount string, asset_id string, private_key string) (string) fee string This is the required fee to send a transaction. from_address This is your asset address. to_address This is asset address of the user whose post you want to read. amount string This is how much you want user A to pay user B to access user B’s posts. asset_id string This the ID of the asset that the dapp owner has created.
What Is OpenBazaar? With OpenBazaar, there is no central server involved at all. It’s a peer-to-peer client to which no government entity can restrict access.
It’s like eBay and BitTorrent had a baby.”
interesting part comes when merchants list their goods on OpenBazaar. It uses the concept of Ricardian contracts to facilitate trade on the network. This is different from smart contracts because they don’t live on a blockchain; instead, they live on the merchant’s computer. A Ricardian contract is basically a way to track the liability of Party A when selling goods to Party B.
Data isn’t stored on a DHT in OpenBazaar; it’s stored locally in a SQLite datastore at each node.
Interesting that it’s not DHT, as a decentralized app
OpenBazaar does use a DHT, but not for data storage. The DHT in OpenBazaar was inspired by Kademlia (like BitTorrent and IPFS) and is used as a sort of “yellow pages” for peers.
Like IPFS, OpenBazaar uses a DHT. Unlike IPFS, OpenBazaar doesn’t accommodate data replication via content-addressed data; no matter how many people want it, the data will only live locally on the originating computer.
Reputation But what about reputation? Reputation is a big part of any marketplace environment; buyers want to be able to trust sellers, and vice versa. In a centralized model, server-owners can hand out reputation to individuals and, with appropriate security, they don’t need to deal with individuals tampering with their own reputation to defraud the system. In a decentralized system, reputation is much more difficult to verify. Trust is dealt with in OpenBazaar through two different types of synergistic systems: global trust and projected trust. When all members of the network trust a
...more
the most important flaw here is the lack of an internal currency.
questionable choice is OpenBazaar’s data storage model: just storing it in a local SQLite datastore with no redundancy or replication.
crowdfunding sites like Kickstarter and Indiegogo take too large a cut of project funding for their work in server maintenance, advertising, hosting, and moderation of crowdfunding projects submitted to them.
geographic limitations on Kickstarter.
certain projects that are impossible to create on Kickstarter because of the rules that the site imposes as a central authority in the name of community standards.
Bitcoin’s scripting language has become more powerful over the years, thanks in large part to the innovations in blockchain technology and Turing-complete smart contract technology coming out of the Ethereum project.
It’s possible to build a Bitcoin implementation that does not verify everything, but instead relies on either connecting to a trusted node, or puts its faith in high difficulty as a proxy for proof of validity. BitcoinJ is an implementation of this mode. In SPV mode, clients can connect to full nodes and download only the block headers. Satoshi described this in his original Bitcoin white paper.
Uber has grown at an exponential rate over the past few years and is showing revenue numbers in the billions.
Riders will be able to spend Zooz tokens to get rides from La’Zooz drivers. Drivers have a different app that lets them “mine” Zooz just for driving around. La’Zooz implements what they call a proof-of-movement
a community roadmap.
The multisig is used as a smart contract that crowd sale buyers can send Bitcoin to and receive Zooz tokens in proportion to the amount they paid. Here are the three possible signers: A trusted member of the Bitcoin community An independent professional auditor A La’Zooz development community representative
DAO Structure La’Zooz aims to be a community-run network, meaning that there is no difference between creators and the users.
DAO establishes itself as a liquid democracy.
data is centralized on their server as well as the wallet node that connects to the Mastercoin network.
The way La’Zooz structured its DAO is commendable. If it has legal contracts requiring those who are listed under the by-laws of its company in Israel to obey the will of the community vote, it has avoided the legal limbo associated with a DAO by complying with local regulation and sticking to the principles of decentralization via liquid democracy. Voting should happen in app as a feature that is just a tab on the sidebar.
Users should opt in to vote; anyone can submit a proposal for a feature request, new regions to focus marketing on, or leadership change. Anyone should be allowed to vote on those proposals.
Jobs in the La’Zooz DAO should be either role-specific or full stack. Full stack professions are already emerging in the startup sector, but in the case of a DAO, full stack must mean not just in terms of engineering, but in terms of playing different roles throughout the company.
Firing should essentially be the equivalent of banning someone in a distributed manner.
La’Zooz shouldn’t use Ethereum for smart contracts until the sidechain proposal is ready.
Finally, La’Zooz shouldn’t concatenate all the instructions for its DAO into one white paper.
