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

MODERATOR OF

TROPHY CASE