Quote from: biophil on September 18, 2014, 02:54:31 PMI haven't decided on the snapshot date yet.
Snapshot date?
When I do I'll post an update about it.
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.
Show posts MenuQuote from: biophil on September 18, 2014, 02:54:31 PMI haven't decided on the snapshot date yet.
Snapshot date?
Quote from: toast on September 09, 2014, 02:28:44 PMYes it would work the same way but it wouldn't make sense to call it something that doesn't have time in the name if its a time-based currency.
So you confirm that the real value is in the user-issued assets and "timeshares" could be called "MEshares" and it would work *exactly* the same way?
Quote from: toast on September 09, 2014, 01:54:35 PM1 hour in TimeShares won't have the value of 1 hour of human time.
I think you are doing it completely wrong. Normal user issued-assets are the best thing for what you are trying to do. Generic "timeshares" will not have value proportional to the value of human time because human time is not fungible.
This is BitShares X or ME except rebranded.
Quote from: theFuzz on September 09, 2014, 01:21:04 PMYes that is how it can workQuote from: CinniDev on September 09, 2014, 01:10:27 PMQuote from: ebit on September 09, 2014, 12:59:30 PM+5% :D
Time Bank?
Welcome! +5%
Thats a better name
Yeh...Really like that. I would imagine the Time would have a value based in the average value across all services? Then you xfer Timeshares tokens to purchase shares in worker's timetokens? So...for instance:
Bob buys 24Hours, looks on the exchange for someone who is offering Web Development Services (Tim). Tim accepts only accepts TimDevHours, which are currently market pegged at a value 50% higher than the average Hour. So Bob uses 1 Hour and 30 Minutes to buy 1 TimDevHour.
Is this how it would work? I think the confusion lies in "what is this time going to purchase?"
Also, when is the snapshot? I'll buy some Cinni if I still get a chance for a chance at more of it--if we can understand this a little better ;)
Quote from: ebit on September 09, 2014, 12:59:30 PM+5% :D
Time Bank?
Welcome! +5%
Quote from: Riverhead on September 09, 2014, 12:42:44 PMYou can spend it on things people are willing to sell for 1 hour of the TimeShares
Ok, add me to the list of confused people then :) .
The name TimeShares - what does it refer to? What is being time shared? Say I have an hour of time...what do I spend it on?
Quote from: feedthemcake on September 09, 2014, 12:27:45 PMIt can be used like a normal coinQuote from: CinniDev on September 09, 2014, 12:20:54 PMQuote from: Riverhead on September 09, 2014, 11:43:12 AM
Cool! Looking forward to seeing how this develops....and maybe getting my self some nice vacation locations :D .
I can see how this can use BitSharesX platform as TimeShares will have different values by location, time of year, current events, weather, etc. A futures prediction market if I ever saw one.
Would the properties be bitAssets?Quote from: Riverhead on September 09, 2014, 12:09:43 PMHey Riverhead
I am thinking it is this:
http://en.wikipedia.org/wiki/Timeshare
This DAC isn't related to real timeshares
Maybe the name suggests that it does.
If you have suggestions on a different name that would suite the project better that would be nice.
However what you said is a great idea and maybe bitassets can be made for them.
I'm confused. What exactly would the "timeshares" be used for? What is their value?
Quote from: Riverhead on September 09, 2014, 11:43:12 AM
Cool! Looking forward to seeing how this develops....and maybe getting my self some nice vacation locations :D .
I can see how this can use BitSharesX platform as TimeShares will have different values by location, time of year, current events, weather, etc. A futures prediction market if I ever saw one.
Would the properties be bitAssets?
Quote from: Riverhead on September 09, 2014, 12:09:43 PMHey Riverhead
I am thinking it is this:
http://en.wikipedia.org/wiki/Timeshare
Page created in 0.142 seconds with 12 queries.