Peck by twetch#13280

1M1nEA…ZdzQ Key · twetch

Anyone out there have an answer? @4 @385 @24 @3

twetch#13280 6.5y

Can someone smart explain how you would revoke access to data on the blockchain? Take EHR for example or any sensitive data you own on chain. After granting access, how can you then revoke? Couldn't they still decrypt the block?

What the chain says

Transaction: d3cc69c5fda18c10df35ce4cbc0ac76cd9b3a7f74c53fa4ae86cc0a29be9da68
Block: 630 703
Time: 2020-04-15T14:45:48Z
Signer: 1M1nEAonpTTFqorgVpprtRZ9EvzRZAZdzQ
App: twetch
Type: post
Content type: text/plain
References: f7b26cc9b3519013bcd36d9022de48e27dabf62a9537f8cedf7dc6e203beacd9
Name in tx: twetch#13280

Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.

Signed by 1M1nEAonpTTFqorgVpprtRZ9EvzRZAZdzQ Verified

Reposted by (1)

twetch#2275 Reposted · 6.5y

Replies (4)

twetch#3375 6.5y

1Abd9y…ujrm Key · twetch

Replying to@1M1nEA…ZdzQ

You can only revoke access to someone who has deleted the key you gave him before.

twetch#140 6.5y

13Mcku…Ko3D Key · twetch

Replying to@1M1nEA…ZdzQ

This will be layered, like a token access on top of BSV. This layer system is in control by EHR and they can again anchor these access records back to the chain (a protocol) for transparency. Authorized access will be the easiest thing to control, forever.

twetch#13280 6.5y

1M1nEA…ZdzQ Key · twetch

Replying to@13Mcku…Ko3D

So something like oauth2? Do you think companies like EHR would basically proxy the read/writes to the blockchain rather then end consumers going directly to the blockchain with a key for data? Allowing EHR to keep the underlying keys protected.

twetch#140 6.5y

13Mcku…Ko3D Key · twetch

Replying to@1M1nEA…ZdzQ

I don’t know what they will do, but I think they will keep your keys and not being able to access themselves using splits and some form of access on top for you.

It’s too complicated for me to get my head around, but I believe it will be a great protocol.

Post by twetch#13280

Reposted by (1)

Replies (4)