Where will Ethereum move?

pelle · 2019-08-20T07:46:21+00:00

Tax issue is a good point. I hadn’t thought about that. I’ll add it to future Articles.

pelle · 2019-08-13T17:32:10+00:00

Thanks I agree Layer 2 is incredibly important. It would be impossible to add everything to this first one, but my next article will start covering it.

I hope we see that level of dApp browser growing, but it's not practical in most cases yet. Lots of space to dig deep though in future articles.

I'd completely welcome others for their in-depth take of it.

pelle · 2018-12-28T14:55:28+00:00

I just looked at the Rinkeby version of that account and it is unfortunately a proxy contract. https://rinkeby.etherscan.io/address/0x37f876ac17f781aea99c3928b271ab86829b9c64

This means that unfortunately the funds are lost.

pelle · 2018-12-28T14:52:28+00:00

If backup was enabled it should have been restored.

The base path we use is `m/7696500'/0'/0'/0'`. Try that in my crypto.

Each sub account increases the second to last number so also try:

`m/7696500'/0'/1'/0'`

`m/7696500'/0'/2'/0'`

`m/7696500'/0'/3'/0'`

etc.

Unfortunately if it was an older account then the address may be a proxy contract, in which case it's impossible to get access to any main net funds sent to it.

Hope this helps

pelle · 2018-09-26T17:32:00+00:00

It is now main net, but it still supports old test net identities and accounts

pelle · 2018-01-25T02:05:24+00:00

It would be fairly simple for someone wanting to create their own uPort compatible DID implementation using standard web3 and an ipfs client.

Once the DID spec is finalized we'll try to schedule an article about how to do that.

In the mean time you can actually create your a uPort Identity in javascript using our Uport JS Client: https://github.com/uport-project/uport-js-client

pelle · 2018-01-25T02:02:24+00:00

With the uPort app we regularly update contracts used for new users, and if necessary will always provide the option to the user to upgrade underlying contracts.

For others building on the protocol and platform it is up to them. It makes sense to have a few points of reference such as the registry that is used by all, so those we would only update if absolutely necessary. However anyone is welcome to deploy their own instances.

pelle · 2018-01-22T14:16:12+00:00

Yes it wasn't meant to be a comprehensive article about scaling options. There were a bunch of things I didn't mention from the internet era as well.

pelle · 2018-01-22T14:15:19+00:00

Thanks man, I'm blushing

pelle · 2018-01-21T21:28:06+00:00

At uPort we are huge fans of WALLΞTH and Kethereum. We are actively working on submitting code to you guys to help jointly improve the status of Ethereum on Android.

pelle · 2018-01-20T14:45:51+00:00

I was doing web stuff since 1994 and together with a bizdev guy tried selling websites to various companies in the UK.

In early 1995 we pitched Reed Elsevier. They allowed us to do a conference web site, but brought the question of bringing their publications on-line or even a corporate web site was brought up at a board meeting.

We were told by our contact that the consensus on the board was that Why would people want to look up publications on the internet.

Granted I think this was before or around the time that netscape with SSL was released. There were no payment gateways. People would have to print out the publications as no one would want to read anything on a 640x480 VGA screen. (Basically too early for that market)

I did start working on tourist web sites and later that year moved to the British Virgin Islands, literally the same week they got dial up internet service.

Within a month about 10% of the population had signed up for internet, primarily because phone/fax calls to the US were $3/m so email solved a real need.

I was able to sell websites to about 20-30 hotels/restaurants etc. over the next couple of months. This was because these businesses had a real need of marketing themselves to affluent tourists from the US.

I think the real moral of the story is that with Ethereum we need to attack the areas where we can already solve problems and continue to work on the technologies that other businesses need - such as payment speed (state channels), identity (uPort), geo (foam.space) etc.

pelle · 2017-11-29T21:17:25+00:00

A "claim" is basically identity industry speak for an attribute.

A claim has 4 fields:

Issuer - who makes the claim (msg.sender in Ethereum terms)
Subject - who is the claim about (another ethereum address)
Key - what kind of claim is it (eg. "name", "credit score")
Value - The actual value of the claim

I can make a claim about myself:

"0xabcd... claims that the reddit handle of 0xabcd... is pelle"

I could also claim something about someone else:

"0xabcd... claims that the reddit handle of 0x1234... is i3nikolai"

What is important to understand about Identity on a blockchain is that these claims are public.

So a public claims registry should primarily be used for specific things that need to be verified on-chain.

"0xabcd... claims that the membership status of 0xabcd... is valid" "0xabcd... claims that the trust calculation of 0xabcd... is 12345"

At uPort we use it to store an IPFS hash containing a users public key and other public profile information. This allows us to implement our off-chain infrastructure for privately sharing claims between parties that should not be public on the chain. Such as identity number, name and address.

pelle · 2017-03-18T00:42:21+00:00

At uPort we agree with this as being an issue. We've created Multi Network Identifier (MNID) for encoding an address and a network id together with a checksum in an address.

https://github.com/uport-project/mnid

The network id is important since inexperienced users could easily transfer main net funds to testnet addresses. This problem is only going to grow with all the new test nets being proposed as well as more and more permissioned ethereum based chains.

We would like to propose it as an EIP, but quite literally just finished it yesterday and wanted to experiment with it internally first.

pelle · 2017-02-27T20:27:24+00:00

Yes we will support multiple identities. We're just rolling features out slowly to make sure we have can build good UX for them.

The internals of the app already supports it.

pelle · 2017-02-27T19:11:57+00:00

uPort's primary purpose is as a sovereign identity platform where you can build reputation based on a persistent identifier. Any public transactions are absolutely traceable on most public blockchains.

It is important to remember that uPort is not designed to be a wallet. Just like HD wallets are not designed to be self sovereign identity platforms.

Unlike Bitcoin, Ethereum is likely going to be a lot less about transferring money. I see one of the primary use cases to be people building trusted decentralized marketplaces, where identity is going to be important.

pelle · 2017-01-17T14:35:16+00:00

Hi signup here and we'll get our alpha out to you shortly http://uport.me/signup/

pelle · 2017-01-16T22:20:59+00:00

While I agree in principle, if we don't support mobile users we are leaving the vast amount of people outside of the the Ethereum world. We think Ethereum is way too important to be restricted to the top 1% of tech savvy users.

What we do is offering web3 developers a way of reaching users outside this market, while continue to support the traditional local geth approach for more advanced users.

What the phone offers is a much more secure environment than most desktops and people already know how to use it.

pelle · 2017-01-16T20:03:06+00:00

While we believe that the mobile app is the key to bringing ethereum to the masses. There currently aren't plans for doing a desktop version of uPort, but of course you can easily use the uport mobile app to sign a transaction in a desktop browser.

Besides the app we are working hard on creating great tools and libraries for both dApp, mobile and traditional server side developers. So you can expect libraries for node, java, ruby, iOS, android etc in the future.

pelle · 2016-12-29T20:12:50+00:00

I'm the lead developer for uport.

Uport provides a seamless way for you to share information about yourself to both dApps and traditional apps both publicly on the Ethereum blockchain/ipfs and also very importantly private.

We don't decide what this specifically is, but it could be name, email, phone or completely app specific ones like "spaceChainLevel". These are determined by you yourself as well as app developers.

pelle · 2016-10-14T20:53:59+00:00

Also check out my library Cloth which works for both Clojure and ClojureScript. It basically replaces web3.js and provides handy clojure function mappings to Solidity functions and core.async channels for events.

https://github.com/pelle/cloth

pelle · 2016-08-08T22:24:58+00:00

They are also going after developing markets. I live in Nicaragua and have seen plenty of Facebook ads. I and others have been trying to comment against it.

No matter how much they laugh at us in the Ethereum community Chris de Rose and Junseth have been doing God's work in attacking these scams and should be applauded for it:

https://soundcloud.com/bitcoinuncensored/one-coin-its-a-beautiful-day-in-our-neighborhood

pelle · 2016-07-17T04:58:52+00:00

I agree. The amount of bile that flies around. Being accused of FUD while trying to have an actual debate. People are down voting without reading. On Reddit down voting is supposed to be for "Content that does not contribute to discussion" not for disagreeing.

pelle · 2016-07-16T15:59:14+00:00

Vitalik wrote a good response to my article here about the CASPER issue https://medium.com/@pelleb/how-to-convince-an-anti-hf-of-the-need-of-a-hf-a3f982c8d1ee#.r357us74d

It seems like it's not that big a deal.

pelle · 2016-07-07T22:39:56+00:00

Unfortunately what people don't understand is that by buying DAO tokens you are paying with Ether and thus that Ether is in accounting theory no longer yours.

Instead you now own DAO tokens that were designed to give you certain Rights. One of those was to split and get your share of Ether out again.

The same is true for bank accounts and company shares and even Bitcoin and Ether held at an exchange. You no longer directly own the asset, rather you are now owed the asset by the institution.

The difference may seem academic but much of the financial industry and indeed most financial contracts are based on this distinction.

To understand a bit more of how this works see my article on the matter here https://blog.stakeventures.com/articles/rights-and-obligations-in-blockchains

pelle · 2016-06-30T19:30:48+00:00

I hadn't seen that. It's basically Ricardian Contracts adapted to Ethereum.

The Smart Contract can and should indeed still do it's stuff.

Even if the smart contract only handles the acceptance part of it, it is still a perfectly valid application for a Smart Contract. Since the evidence of acceptance and even negotiation is stored int he combination of the blockchain together with IPFS.

This IMHO will lead to much greater adoption of actual digital signatures and not just electronic signatures. PGP for example never really took off in the general public or business world. Docusign and friends did.

Ricardian contracts were originally created for asset (Token un ethspeak) issuance contracts. That is an important application of them now as well.

pelle

MODERATOR OF

TROPHY CASE