Tokenly by Adam B. Levine - Token Controlled Access

[Average Guy on Street]

Thanks for the insights Luckybit.

I agree with you Bob. Peertracks (or streaming services in general) would make a good solution for audio books.

[bobmaloney]

The audiobook example sounded to me as something that could be done through MUSE and Peertracks.

If not, what is missing from MUSE and Peertracks that would prevent providing those services?

[luckybit]

Practical uses for CP-ABE or ABE in general would be if you have decentralized reputation, where you can factor in what the entity has done, what attributes the entity has,  and the entities would not have to know that their attributes give them decryption capabilities of certain ciphertext.

From the perspective of the community, random entities would have access do to their attributes which would have been decided on in advance by the developers.  You could probably do this with tokens but with a token then it's obvious that entities have a certain token, or that entities have access. Attribute based would mean no one would need to know who the entities are, they could be anonymous entities.

So if you're talking about bots, or DACs, or individuals, any of these could be among the anonymous entities as long as they meet the attributes in the policy to unlock the decryption. Mike Hearn mentioned CP-ABE when discussing the idea of distributed markets, but the state of the art in encryption has advanced quite a bit since then so a lot more is possible today than was back then: https://en.bitcoin.it/wiki/Distributed_markets

[luckybit]

In case you missed the recent Lets Talk Bitcoin podcast, about Adam B. Levine's Token Controlled Access project called TOKENLY.

Pretty interesting stuff!

Here's the link:
https://letstalkbitcoin.com/blog/post/lets-talk-bitcoin-239-solving-problems


I'd love to read some thoughts by some of the Bitshares Developers about this particular podcast

It's a good idea, token based access control. Generally though, you can do better with smart contracts with Ciphertext Policy-Attribute Based access control schemes. In that setup you could determine precisely the set of attributes or (reputation) that must be needed to gain access.

CP-ABE or CP-ABE-HP would be how you could expand token based access control.

. However, ABE has a privacy problem: The access
policies are sent in clear along with the ciphertexts. Further generalizing the idea
of policy-hiding in cryptographic access control, we introduce policy anonymity
where – similar to the well-understood concept of k-anonymity – the attacker can
only see a large set of possible policies that might have been used to encrypt,
but is not able to identify the one that was actually used. We show that using a
concept from graph theory we can extend a known ABE construction to achieve
the desired privacy property

https://crypto.stackexchange.com/questions/17893/what-is-attribute-based-encryption
https://scholar.google.com/scholar?q=ciphertext+policy+attribute+based&btnG=&hl=en&as_sdt=0%2C5&as_ylo=2015
http://www.ijsr.net/archive/v3i1/MDIwMTM3Mzk%3D.pdf
https://eprint.iacr.org/2011/255.pdf
http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=6824572

[Average Guy on Street]

In case you missed the recent Lets Talk Bitcoin podcast, about Adam B. Levine's Token Controlled Access project called TOKENLY.

Pretty interesting stuff!

Here's the link:
https://letstalkbitcoin.com/blog/post/lets-talk-bitcoin-239-solving-problems


I'd love to read some thoughts by some of the Bitshares Developers about this particular podcast