BitShares Forum

Specific Projects => Muse/SoundDAC => Topic started by: cob on April 08, 2016, 06:09:24 pm

Title: Early 2nd quarter 2016 update
Post by: cob on April 08, 2016, 06:09:24 pm
Setback and missed deadline
Let’s get the obvious and negative part of this update out of the way first.
We said we would have something to show by now, which didn’t materialize.
I was able to show you part of what we had done so far through the two walkthrough videos of the PeerTracks platform, which is done and functioning well.
But PeerTracks requires a stepping-stone (Troopeers) before it can launch, which is what we intended to finalize and release near the end of 1st quarter of 2016.

For those that don’t know, Troopeers is PeerTracks, the non-music-specific aspect of it. It allows anyone that has or wants a fan base to create his token so that he may be discovered, funded, etc. Troopeers is simply an extension that of the original objective that tackles other markets such as sports, acting/movies, instagram stars, streamers, etc. The music branch of Troopeers is PeerTracks – that branch requires its own, more complex, feature set (music player, royalty splitter, etc).

As you may remember, we required internal developers rather than relying on external firms.  This was our first delay.  We had everything ready to go business wise, but no internal devs! We eventually did find someone highly qualified and so Troopeers was thus being built out in early 2016.  Our new developer moved fast, first learning about our project, then Graphene, MUSE, etc.  He picked up everything in no time and was the main dev in charge of the Troopeers web app (and finalizing PeerTracks’ MUSE integration).  We were very happy with the progress.  Unfortunately, a matter unrelated to PeerTracks required him to step away.  This unfortunate event brought us back to square one regarding hiring of internal devs.  Finding replacements and getting them up to speed would mean there was no chance in hell of achieving our objective of launching Troopeers in time.

Instead of telling you how the problem was solved, let me ride this wave of negative news with another kicker.


Graphene’s architectural shortcomings
Graphene was set up back in the day where it was thought that everyone would run their own node or download a client on their machine. The codebase still reflects that.

What we need is something that can provide an excellent UX while being scalable to millions.
Graphene’s wallet infrastructure makes it possible to host a mere few dozen wallets per virtual machine. This, of course… is not scalable to our needs.

A good solution to this is to have the wallets web based – browser side wallets.

The issue with THAT is that the JavaScript code for the browser side wallet was converted from C++ by an automatic converter making the code huge! (68 megabytes according to BitSapphire)

Loading such a large JS would be a nightmare for anyone trying to access Troopeers and PeerTracks from any phone/tablet/laptop no matter how fast your Internet connection is. Basically the code is far from optimized for this scenario, but it could be reengineered and be brought down to a more reasonable size (under 2 MG)

This is actually the exact problem BitSapphire is attempting to tackle with Moonstone. They are re-writing the JavaScript to solve this very issue.


Now that my excuses are out of the way...






We are launching a consumer-facing product in MAY!

Found amazing developers!
Turns out the person that told me about BitShares, back in 2013, which I trust, is a hands-on coder. I thought he just knew everything about crypto as an early adopter. I didn’t know he was actually proficient in using the MEAN stack and Blockchains. He also has a ton of stake in BitShares and MUSE so is already highly incentivized to see this project succeed.
And so we’ve hired both him and his business partner (equally qualified!) to launch Troopeers, then PeerTracks. To top it all off, they are both located in Montréal (near me) and so I will be working with the team, hands-on, in the same physical space.

PeerTracks inc. finally has the piece that was missing in order to bring this idea to market.

Graphene workaround
Like life in general, problems usually lead to creative solutions since you are forced to look at situations from new angles. The solution we came up with is one that we have always ignored; it wasn’t even in the cards as far as we were concerned.

Phase 1 of PeerTracks (Troopeers) is hitting the market with a centralized database.

The goal is to ONRAMP people into the system with an excellent UX. The system is fast and responsive on any standard device – mobile from the get-go. It is scalable to millions and there is no crypto for the (non-techy) users to worry about. No need to educate anyone on public/private key cryptography while acquiring users. No need to have users remember a passphrase, backup keys/wallets and risk loosing everything. Nor do we need to hold any keys.

We are going full throttle with user acquisition. The community can finally have something to push and promote: An online, released product.

Every single user, from celebrities to token holding fans, and all token balances, will be snapshotted from our internal database, onto MUSE once the blockchain is ready for the heavy lifting required of it. In the meantime, everything will take place on our transparent – although temporarily centralized – database.

Stars/celebrities will be able to create their profiles and their limited edition tokens.
Fans will be able to show up and support their stars by using credit card to purchase tokens and take part in tipping and patronage.
Two-way interaction will be made possible with our weighted inbox.
Stars will be able to reward their troops with perks and giveaways.
Advertisers will be able to target specific fan bases using the token system.

Once complete, all token balances will be hardforked into MUSE. Tokens will essentially go from being an entry in our database to becoming a crypto-token on the MUSE blockchain.

Note that the current MUSE blockchain will still be operational during these stepping stone times, but it will serve only as a way to own and trade stake in the future, improved version. I should also mention that we now have a Graphene expert on board which monitors the MUSE chain and can update it whenever need be.


Advantages to the centralized stepping stone



The takeaway is that the objective is the exact same as always – a decentralized network for music metadata, royalty payments and tokens. We merely found a way to make users acquisition seamless. Release will be faster and by phases. We no longer need to have everything blockchain be perfect before we start getting people on board and test out the market’s reaction.


TL;DR
We have new devs
We are Launching Troopeers in MAY
Its database will be centralized (temporarily)
MUSE will be able to rise in value sooner rather than later
Our internal database will be snapshotted to MUSE 2.0




Title: Re: Early 2nd quarter 2016 update
Post by: Marky0001 on April 08, 2016, 06:23:53 pm
 :o :D
Title: Re: Early 2nd quarter 2016 update
Post by: xeroc on April 08, 2016, 06:26:22 pm
Good news
Title: Re: Early 2nd quarter 2016 update
Post by: tbone on April 08, 2016, 06:30:57 pm
I'm happy with this.
Title: Re: Early 2nd quarter 2016 update
Post by: giant middle finger on April 08, 2016, 06:42:49 pm
LIES!!!


FUD!!!


FAKE FAKE FAAAAAKE!!



SELL!!


SELLLL!


SEEEELLLLLLLLL!!!!!


















(to me)

 8)
Title: Re: Early 2nd quarter 2016 update
Post by: Akado on April 08, 2016, 06:46:05 pm

For those that don’t know, Troopeers is PeerTracks, the non-music-specific aspect of it. It allows anyone that has or wants a fan base to create his token so that he may be discovered, funded, etc. Troopeers is simply an extension that of the original objective that tackles other markets such as sports, acting/movies, instagram stars, streamers, etc. The music branch of Troopeers is PeerTracks – that branch requires its own, more complex, feature set (music player, royalty splitter, etc).

So the muse token represents solely the music branch of Troopeers? So if you want to go towards other branch like sports or movies, it will have to be done on a different chain? Or it can be done all on the same chain and our current token represents all the branches Troopers can reach out to?
Title: Re: Early 2nd quarter 2016 update
Post by: rajarush on April 08, 2016, 06:49:09 pm
We are launching Ptrack, blabla  when? Wait, Before that we need to launch Tpeer, blabla. U asked When? Listen, Before that we need to launch AShare. When is that? Not yet, I will soon release Bshit, here is why...anyway, the very first step is to launch peercrap when will be out in May!

Cheers!


Sent from my iPhone using Tapatalk
Title: Re: Early 2nd quarter 2016 update
Post by: cob on April 08, 2016, 07:13:56 pm
So the muse token represents solely the music branch of Troopeers? So if you want to go towards other branch like sports or movies, it will have to be done on a different chain? Or it can be done all on the same chain and our current token represents all the branches Troopers can reach out to?

Everything will take place on the MUSE blockchain.

So George Clooney tokens, Elon Musk Tokens and our beloved Justin Bieber Tokens will all rest and trade on MUSE.

So will the automatic splitter which anyone can use but it will mostly be used by the musicians on MUSE since it brings much needed added value to their industry above all others.

Title: Re: Early 2nd quarter 2016 update
Post by: Ben Mason on April 08, 2016, 09:05:16 pm
Cob, thank you for explaining the situation. I am very happy with the solution to the issues you've discovered and the challenges you've faced. It sounds like you've all been on quite a roller-coaster. So May! Incredible!

I think it is exceedingly important to keep everyone updated regularly regarding the transition from centralised to decentralised. I'm not interested in a successful new centralised and potentially corruptible media revolution....despite how fun it will be seeing artists and fans begin using the incredible applications you've been building.

Good luck. So impressed you've stayed the course through everything.
Title: Re: Early 2nd quarter 2016 update
Post by: woolcii on April 09, 2016, 02:10:02 am
cool



从我的 iPhone 发送,使用 Tapatalk
Title: Re: Early 2nd quarter 2016 update
Post by: donkeypong on April 09, 2016, 03:33:56 am
Cob, thanks for the honest and comprehensive update. This is a very complex project and it sounds like you've steered it through a lot of obstacles. Rome wasn't built in a day; delays are par for the course with projects like this. Of course, I strongly look forward to the day when we have an awesome product to promote and grow.
Title: Re: Early 2nd quarter 2016 update
Post by: BunkerChainLabs-DataSecurityNode on April 09, 2016, 05:21:11 am

Graphene’s architectural shortcomings
Graphene was set up back in the day where it was thought that everyone would run their own node or download a client on their machine. The codebase still reflects that.

What we need is something that can provide an excellent UX while being scalable to millions.
Graphene’s wallet infrastructure makes it possible to host a mere few dozen wallets per virtual machine. This, of course… is not scalable to our needs.

A good solution to this is to have the wallets web based – browser side wallets.

The issue with THAT is that the JavaScript code for the browser side wallet was converted from C++ by an automatic converter making the code huge! (68 megabytes according to BitSapphire)

Loading such a large JS would be a nightmare for anyone trying to access Troopeers and PeerTracks from any phone/tablet/laptop no matter how fast your Internet connection is. Basically the code is far from optimized for this scenario, but it could be reengineered and be brought down to a more reasonable size (under 2 MG)

This is actually the exact problem BitSapphire is attempting to tackle with Moonstone. They are re-writing the JavaScript to solve this very issue.


Now that my excuses are out of the way...


This has no semblance to reality.

If Bitsapphire claims they can't develop Moonstone because of this javascript boogieman that nobody else here has ever even seen or heard of.. how the heck did this happen? https://www.youtube.com/watch?v=ZLObFOPIzIM&index=13&list=PLjbx3qSmDe7RYkRMIEuFyYyG7_vvKgou0

They didn't take $35k from community members to get a working mobile wallet either. Meanwhile a supposed team of experts in blockchain have failed to deliver even an alpha after an ENTIRE YEAR.

I think it is time that Moonstone returned the funds they took from everyone.. they have not delivered and clearly are in an endless loop (programmer pun intended) of only delivering excuses.

Sorry but the platform we have is MORE than adequate and handles FAR more than what is stated above even right 'now'.

The rest of the update sure.. fine.. but this part about not launching with graphene because of false claims I take issue with.

If I am off my rocker (again, this time with a music pun), then please provide the proof from bitsapphaire regarding these claims. It would be in their best interest also.
Title: Re: Early 2nd quarter 2016 update
Post by: jwiz168 on April 09, 2016, 05:50:38 am
Great it is worth the wait... +5%
Title: Re: Early 2nd quarter 2016 update
Post by: svk on April 09, 2016, 06:38:13 am

Graphene’s architectural shortcomings
Graphene was set up back in the day where it was thought that everyone would run their own node or download a client on their machine. The codebase still reflects that.

What we need is something that can provide an excellent UX while being scalable to millions.
Graphene’s wallet infrastructure makes it possible to host a mere few dozen wallets per virtual machine. This, of course… is not scalable to our needs.

A good solution to this is to have the wallets web based – browser side wallets.

The issue with THAT is that the JavaScript code for the browser side wallet was converted from C++ by an automatic converter making the code huge! (68 megabytes according to BitSapphire)

Loading such a large JS would be a nightmare for anyone trying to access Troopeers and PeerTracks from any phone/tablet/laptop no matter how fast your Internet connection is. Basically the code is far from optimized for this scenario, but it could be reengineered and be brought down to a more reasonable size (under 2 MG)

This is actually the exact problem BitSapphire is attempting to tackle with Moonstone. They are re-writing the JavaScript to solve this very issue.


Now that my excuses are out of the way...


This has no semblance to reality.

If Bitsapphire claims they can't develop Moonstone because of this javascript boogieman that nobody else here has ever even seen or heard of.. how the heck did this happen? https://www.youtube.com/watch?v=ZLObFOPIzIM&index=13&list=PLjbx3qSmDe7RYkRMIEuFyYyG7_vvKgou0

They didn't take $35k from community members to get a working mobile wallet either. Meanwhile a supposed team of experts in blockchain have failed to deliver even an alpha after an ENTIRE YEAR.

I think it is time that Moonstone returned the funds they took from everyone.. they have not delivered and clearly are in an endless loop (programmer pun intended) of only delivering excuses.

Sorry but the platform we have is MORE than adequate and handles FAR more than what is stated above even right 'now'.

The rest of the update sure.. fine.. but this part about not launching with graphene because of false claims I take issue with.

If I am off my rocker (again, this time with a music pun), then please provide the proof from bitsapphaire regarding these claims. It would be in their best interest also.
I agree, those claims about Graphene are just wrong. It was not setup like that, on the contrary it was built to address issues like that in BTS 1 which did have scaling issues of that type. One of the main points of Graphene was that no one would be required to run their own node!

Most likely Bitsapphire is feeding you lies to cover their tracks. There's no reason for them to rewrite the js from scratch or compile it from c++  (lol) instead of using jcalfee's brilliant js implementation which is used in the default GUI.
Title: Re: Early 2nd quarter 2016 update
Post by: bitacer on April 09, 2016, 09:22:53 am
I am glad I sold my MULES without any loss. This might end up just like its cousin doomstone or whatever its called. 
Title: Re: Early 2nd quarter 2016 update
Post by: Marky0001 on April 09, 2016, 09:43:27 am
wait... is this moonstone clown cob`s cousin???

Wow. that makes me confused  ::)

P.S.: Why are you talking about C++? Isnt C# the better choice?

Please explain what is this all about with Bitsapphire ? If this is the moonstone guy who screwed up the moonstone project this whole update gets a bad taste somehow
Title: Re: Early 2nd quarter 2016 update
Post by: Philogus on April 09, 2016, 11:21:56 pm
The Ethereum blockchain is up and running: it just works. 
Title: Re: Early 2nd quarter 2016 update
Post by: woolcii on April 13, 2016, 02:17:41 am
We are launching Ptrack, blabla  when? Wait, Before that we need to launch Tpeer, blabla. U asked When? Listen, Before that we need to launch AShare. When is that? Not yet, I will soon release Bshit, here is why...anyway, the very first step is to launch peercrap when will be out in May!

Cheers!


Sent from my iPhone using Tapatalk
cool
Title: Re: Early 2nd quarter 2016 update
Post by: Riverhead on April 13, 2016, 02:31:02 am
The Ethereum blockchain is up and running: it just works. 
  • Contact the guys at UjoMusic: http://ujomusic.com/ (http://ujomusic.com/)
  • Negotiate a merger between Peertracks and UjoMusic.
  • Launch the new Peertracks Dapp on the Ethereum blockchain.

You realize to implement everything MUSE wants to do you'd basically have to recreate Bitshares on Ethereum. That would be an entire suite of smart contracts to handle ad hoc user issued assets and market pegged assets. I like Ethereum and am actively involved in a big Ethereum project but it's not the golden screwdriver. If Peertracks were to release on Ethereum it would push release out 8 - 12 months.

Also keep in mind that MUSE is not Peertracks. If you push Peertracks to Ethereum then MUSE is dead unless another business can be found to release on the platform. Be careful what you wish for.
Title: Re: Early 2nd quarter 2016 update
Post by: Ben Mason on April 28, 2016, 10:45:36 am
Hi Cob,

How goes the preparations for launch in May?  Are you gearing up for a marketing drive?  Will you be able to let the Muse holders know how they might be able to help?

Cheers,

Ben.
Title: Re: Early 2nd quarter 2016 update
Post by: karnal on April 28, 2016, 11:04:13 am
The stuff about wallets per virtual machine.. priceless.
Title: Re: Early 2nd quarter 2016 update
Post by: inarizushi on April 28, 2016, 12:20:17 pm
The stuff about wallets per virtual machine.. priceless.

Sounds like a Deepak Chopra quote... credibility, where art thou?
Title: Re: Early 2nd quarter 2016 update
Post by: LoveYouMakMak on May 13, 2016, 02:28:10 pm
Hi Cob,

How goes the preparations for launch in May?  Are you gearing up for a marketing drive?  Will you be able to let the Muse holders know how they might be able to help?

Cheers,

Ben.

Update?
Title: Re: Early 2nd quarter 2016 update
Post by: sudo on May 28, 2016, 04:49:25 pm
no update
Title: Re: Early 2nd quarter 2016 update
Post by: chryspano on May 28, 2016, 06:02:21 pm
https://steemit.com/muse/[member=2216]cob[/member]/peertracks-troopeers-and-muse-community-update

[EDIT]
Copy paste the whole link to your browser



Title: Re: Early 2nd quarter 2016 update
Post by: Marky0001 on May 28, 2016, 06:53:28 pm
Smells like
Title: Re: Early 2nd quarter 2016 update
Post by: LoveYouMakMak on May 29, 2016, 08:30:48 pm
Smells like

more bs?
Title: Re: Early 2nd quarter 2016 update
Post by: Frodo on June 02, 2016, 12:14:21 pm

We are launching a consumer-facing product in MAY!

(https://cdn.meme.am/instances/500x/57998285.jpg)
Title: Re: Early 2nd quarter 2016 update
Post by: lil_jay890 on June 02, 2016, 02:40:48 pm
They are taking a page out of Stan's book... I'm sure they will have no problem launching in May as long as they don't specify which year they plan to launch...
Title: Re: Early 2nd quarter 2016 update
Post by: Ander on June 02, 2016, 08:17:20 pm
They are taking a page out of Stan's book... I'm sure they will have no problem launching in May as long as they don't specify which year they plan to launch...

May of 2022 is going to be huge for MUSE. :P
Title: Re: Early 2nd quarter 2016 update
Post by: jwiz168 on June 03, 2016, 12:06:42 am
In the crypto world this delay should be understandable. If it was a new player in the field MUSE might well be in an ICO , just as the rest of 3rd generation digital assets popping out lately. Devs are aware the BITCOIN HALVING effect. They will wait and see if what will happen.  Might as well take advantage of the situation.
Title: Re: Early 2nd quarter 2016 update
Post by: Marky0001 on June 06, 2016, 09:51:39 pm
does delays have not been communicated properly... instead of telling us what is happening with the project promises how great they will be in may, etc.

he is the worst crypto guy i have seen so far.

Other scammers at least ran and never came back, but he is teasing us and avoids the major questions.
Title: Re: Early 2nd quarter 2016 update
Post by: gamey on June 06, 2016, 10:04:08 pm

If he hasn't just left and went silent he's actually better than all your scammers. If you think he is teasing you just sit on your tokens. There has to be some reason he sticks around.
Title: Re: Early 2nd quarter 2016 update
Post by: Marky0001 on June 07, 2016, 07:08:31 am

If he hasn't just left and went silent he's actually better than all your scammers. If you think he is teasing you just sit on your tokens. There has to be some reason he sticks around.

No, there is no real world reason why he is silent... It is because he has to put out updates that keep the people silent for weeks and month by month more and more people loose interest and stop investigations.

Again... Check out ltcgear scam 2014/15.

Absolutely the same behavior 100%.

Don't you wonder why cob never answers the most relevant questions? He simply keeps silent and there is no business reason for that.

He simply doesn't have an answer and instead of being sucked into more lies he ignores them.

There is a pile of crap that has been posted and said by cob in the last 18months.

He doesn't give a crap about it because he knows no one will go and read old threads.

Currently he is active on STEEM but also there people tell him to fuck off and work on muse instead of posting crap in the forums
Title: Re: Early 2nd quarter 2016 update
Post by: LoveYouMakMak on June 07, 2016, 11:15:27 pm

If he hasn't just left and went silent he's actually better than all your scammers. If you think he is teasing you just sit on your tokens. There has to be some reason he sticks around.

Butterfly Labs. Excuse after excuse.
Title: Re: Early 2nd quarter 2016 update
Post by: Marky0001 on June 08, 2016, 12:40:18 am

If he hasn't just left and went silent he's actually better than all your scammers. If you think he is teasing you just sit on your tokens. There has to be some reason he sticks around.

Butterfly Labs. Excuse after excuse.

Thank you... Another great example!