Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - cob

Pages: 1 [2] 3 4 5 6 7 8 9 ... 26
16
Muse/SoundDAC / Re: Why so silent?
« on: June 14, 2016, 03:57:34 pm »
Hi Cob, thanks for posting.  I just have one question.  Why are you and your team focusing on the b2b approach when it certainly looked like you were almost ready with an MVP for Peertracks months ago?

Let me go into more detail.

The PeerTracks web app is pretty much ready. The royalty splitter needs something to split.
One big issue is the stability of the bitUSD (collateralized by MUSE). MUSE is too volatile to support a MUSE-USD.
Our users are not traders. The music industry is quick to sue for minor royalty discrepancies.
PeerTracks faced a chicken/egg problem.

The second problem was the double pitch (pitched the token concept along with the automatic payment splitter/distributed metadata ledger)

I solved two birds with one stone by focusing on Troopeers. It's a single pitch. "Whoever you are, if you have or want an engaged fanbase, sign the hell up!"
The onramping is easy with a centralized DB as a back end. We will then snapshot all token balances to MUSE once the blockchain is to a point we are happy with.

This means that Troopeers can do its thing, irrespectively of MUSE. MUSE can be upgraded to something much more viable. Only then will the music branch launch (PeerTracks.com)

We simply can't afford a giant team though, so progress is slow. Troopeers' success should allow us a much much bigger budget.

ATM ressources are focused on Troopeers. Shortly switching gears to MUSE. Then we hook up Troopeers to MUSE, followed by PeerTracks.

17
Muse/SoundDAC / Re: Community sentiment - cob screwed us?
« on: June 14, 2016, 03:39:22 pm »
I'd hate to bring water to the mill but I'd like to respond to concerns.

This isn't or wasn't a scam. We aren't anonymous guys. Funds were spent where they appeared required.
And we were INVITED to "those fancy events" they didn't incur huge expenses. I almost regret sharing the pictures the events, but I don't (:
The project got industry attention. Delivery is what is missing.  Luckily Troopeers has started being demo'd. We'll soon have the metrics (users, income, eyeballs) required to move onto the next phase.

Ben is correct I'm not at the helm,  I initiated the project and a week later, Daniel introduced me to Eddie, PeerTracks CEO... possibly reptilian.

18
Muse/SoundDAC / Why so silent?
« on: June 07, 2016, 06:36:52 pm »
Have we ever been vocal?

Hey everyone.

The plan is the same as last explained. Troopeers MVP is the focus: B2B approach. We already have some interest in plugging into our (non existing!) API so that multiple third party sites get to raise funds and engage their artist's/celebs fan base. We are happy there is market validation of the concept!

I am sorry that it won't provide any short-term direct value to MUSE. It serves as on-ramping celebs (and wannabe celebs) into a platform that will later on be snapshotted onto MUSE.

Just so you know. At the moment Troopeers is loaded up with fake content only for demo purposes. A bunch of fake profiles, fake tokens, fake fans and fak fan2star conversations.
Should be able to show it off to the community soon.

Soon ain't a date though d:    I know

19
Muse/SoundDAC / Quick may update
« on: May 19, 2016, 11:15:08 pm »
Greetings everyone.

Someone on Slack suggested I update the community through STEEM, which is genius. So here we go!

https://steemit.com/muse/[member=2216]cob[/member]/peertracks-troopeers-and-muse-community-update

20
Muse/SoundDAC / New faucet up and running
« on: April 25, 2016, 06:17:10 pm »
If you use the Faucet address "http://192.241.190.227" .. you can register accounts again.

Nice work Xer0c!

21
Muse/SoundDAC / Re: Early 2nd quarter 2016 update
« 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.


22
Muse/SoundDAC / Early 2nd quarter 2016 update
« 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

  • Hit the market immediately – in May
  • This is the speedboat approach for user acquisition
  • Great UX
    • Fast & responsive
    • Scalable
    • No crypto keys to manage
  • No chargebacks (they can happen but we can revoke token ownership in case of chargeback) a major concern when dealing with credit cards
  • Our internal database is transparent
  • Token balances/ownership on our internal database is snapshotable
  • MUSE’s market cap will still grow to reflect the success of the project
  • Faster to develop
  • Gives time to CNX, BitSapphire and crypto world in general to develop better blockchain tech – gives us more and better options when we upgrade MUSE
  • Gives time to the music-industry to figure out the Minimal Viable Data set Benji Rogers is pushing for
  • We can launch a proto-PeerTracks, with a music metadatabase, the royalty payment splitter and artist tokens – all of which will be snapshotted to MUSE
  • Our PR firm, marketing experts and other resources can begin doing what they do best


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





23
Muse/SoundDAC / Re: Whats the status of MUSE now?
« on: April 05, 2016, 03:34:41 pm »
I'm pushing out an official update shortly!

With approximate dates and all ^^

There's one unknown that should be resolved by thursday. So expect something a few days after that.

24
This is amazing. Truly a great find!

25
With the new update of BitShares that just came out, [member=94]pc[/member] had time to roll in those new bug fixes as well.

Full nodes get it here!

https://github.com/peertracksinc/muse/releases/tag/1.0.160330

26
The hardfork will occur at 2016-04-02 12:00:00 UTC (i. e. at noon UTC)


https://github.com/peertracksinc/muse/releases/tag/1.0.160330

Only full nodes must upgrade. Otherwise don't worry about it :)

27
Muse/SoundDAC / PeerTracks basic walkthrough video
« on: March 10, 2016, 07:36:33 pm »
These are not promo videos. Just screen capture to get an idea of the platform.

We don't go into the Token - the core value proposition - in these videos. We focus more on the royalty side of things.

The Token system will be made obvious through Troopeers (which is being integrated to MUSE atm)

Fan side vid:
https://youtu.be/aQM4P7uFgk4

Artist side vid:
https://youtu.be/yWOUJehIfJc

28
OMG YES!

This sounds exactly in line with my thinking. If I didn't have an important Skype call in 40 minutes I would listen to this now... Must save for later.

Thanks for the share!

29
Muse/SoundDAC / Re: Peertracks Muse Slack (Unofficial)
« on: February 24, 2016, 06:55:01 pm »
Excellent!

30
Muse/SoundDAC / Re: Can't claim MUSE from the Peertracks preSale
« on: February 23, 2016, 09:29:55 pm »
Ensure you are also running the most recent version.

https://github.com/peertracksinc/muse/releases

Pages: 1 [2] 3 4 5 6 7 8 9 ... 26