That's a great idea, we just an application that can enable it between users.... I wonder if @loon3 could build this into the Companion :)

@adam so you're saying that this is not too difficult, technically speaking? I thought all of this required a soft fork to even be feasible.

edit: another idea.. you're working on token-controlled access, which could have a use here. for example, a common way to show a preview video to a client is to upload it (with a watermark) to vimeo and put a password on it. then disable downloading til they pay. maybe tokens could control access to the content, so that I would "lock" the video with a token, then when I recieve the payment, I send that token to the client. tokens could even be used to overlay or remove watermarks, but that adds another layer of complexity.

Posted on June 8, 2015 at 12:23 PM Last Edited: June 8, 2015 at 12:47 PM

That's a great idea, we just an application that can enable it between users.... I wonder if @loon3 could build this into the Companion :)

@adam so you're saying that this is not too difficult, technically speaking? I thought all of this required a soft fork to even be feasible.

This would definitely not require a hardfork, I was talking with @loon3 about this in the LTBn slack and as he's pointed out here, it's already possible in Bitcore which is used extensively in the companion so if someone wants to try building it in, make it so :)

We don't have the resources to devote to something like this right now but I don't think it would be very difficult, mostly you'd need a designer to really figure out what freelancers would want from the interface and what information is important to the users.