BitShares Forum
Main => General Discussion => Topic started by: Stan on July 19, 2015, 11:24:13 pm
-
ANNOUNCEMENT 6 - Low Cost BitShares ATM Offers New On and Off Ramps
The nice thing about living in a decentralized ecosystem, is that there is absolutely no requirement to have a Central Plan. It's also nice that when such a non-existent Central Plan falls through in a manner which is not the fault of the present author, there is always somebody else to step up and carry the flag forward. Such is the case of this week's announcement which appeared miraculously at the last minute on Saturday.
So, by unanimous consent of the two people who called it to our attention, it becomes ex post facto and ex niliho our official Announcement of the Week (not that we are saying there are supposed to be announcements every week).
Here's the whole exciting dual thread to enjoy, while we scramble to come up with an article to syndicate about it.
I have the impression that this topic is worth being considered as a summer announcement:
https://bitsharestalk.org/index.php/topic,17608.0.html (https://bitsharestalk.org/index.php/topic,17608.0.html)
which is a continuation of an older thread:
https://bitsharestalk.org/index.php/topic,16490.0.html (https://bitsharestalk.org/index.php/topic,16490.0.html)
@Stan, are you in contact with these guys?
IMO they are doing an amazing job and it looks like they are going to deliver on their promises pretty soon.
A thousand years from now, who'll know the difference about when exactly this became our Summer Announcement Number Six?
-
+5%
-
+5%
-
By looking at this thread
https://bitsharestalk.org/index.php/topic,17640.0.html (https://bitsharestalk.org/index.php/topic,17640.0.html)
I think what they need the most right now is coordination with the new 2.0 API and being up-to-date with the 2.0 release schedule.
-
By looking at this thread
https://bitsharestalk.org/index.php/topic,17640.0.html (https://bitsharestalk.org/index.php/topic,17640.0.html)
I think what they need the most right now is coordination with the new 2.0 API and being up-to-date with the 2.0 release schedule.
I think, once there is an API freeze, the devs are going to publish a documentation for it!
-
+5% +5% +5%
-
+5% +5% +5%
-
Absolutely incredible. I love it.
-
Great! I think it's less about the announcement but keeping up the thought of doing a weekly rhythm of communications. Even a post of no news to report was good. Consistency to plans is important to perception at this time.
-
Thank you!
I'm still trying to sort out a problem with the bitshares wallet server. Something broke when I moved the environment from development to live. There are enough changes here that it's a bit like whack-a-mole. Hardware is waiting to ship, probably another day or so left on software though. Getting there, but so I don't have to monitor 3 threads if you have questions about the ATMs that aren't answered in the FAQ keep the discussion over on this one... https://bitsharestalk.org/index.php/topic,17608.15.html thanks!
-
Thank you!
I'm still trying to sort out a problem with the bitshares wallet server. Something broke when I moved the environment from development to live. There are enough changes here that it's a bit like whack-a-mole. Hardware is waiting to ship, probably another day or so left on software though. Getting there, but so I don't have to monitor 3 threads if you have questions about the ATMs that aren't answered in the FAQ keep the discussion over on this one... https://bitsharestalk.org/index.php/topic,17608.15.html thanks!
Welcome aboard @devlux ! Don't hesitate to contact my anytime ... if you'll need something graphical related ...
-
Thank you!
I'm still trying to sort out a problem with the bitshares wallet server. Something broke when I moved the environment from development to live. There are enough changes here that it's a bit like whack-a-mole. Hardware is waiting to ship, probably another day or so left on software though. Getting there, but so I don't have to monitor 3 threads if you have questions about the ATMs that aren't answered in the FAQ keep the discussion over on this one... https://bitsharestalk.org/index.php/topic,17608.15.html thanks!
If you want to give us a rough draft press release with a picture of your product or someone's smiling face, we can take it from there.
-
Awesome stuff! +5%
-
Thank you everyone. I'm point of contact on technical matters such as system specs etc. Alec Hahn @bitcoin42 is CEO and should be the person to coordinate with for pictures and pricing details, press releases etc.
In otherwords if it's broke, not working, or otherwise technical I'm your guy, otherwise it's Alec :)
-
+5% ;D
-
I've asked marketing to come in and help...
(http://cdn2.hubspot.net/hub/53/file-27425252-jpg/superhero.jpg)
-
dead project,no news since july.
-
http://bitcoin42.com/blog/can-you-believe-its-almost-here/
We are busy bee's. Website was down for a few days which caused confusion. We'll ramp up a complete new page just for this baby. There will be four models. "Simplicity" (small one way), "Complexity" (small two way), "Visibility"(large one way), "Capacity" (large two way).
Simplicity will be ready sooner than later. No worries. ;)
-
http://bitcoin42.com/blog/can-you-believe-its-almost-here/
We are busy bee's. Website was down for a few days which caused confusion. We'll ramp up a complete new page just for this baby. There will be four models. "Simplicity" (small one way), "Complexity" (small two way), "Visibility"(large one way), "Capacity" (large two way).
Simplicity will be ready sooner than later. No worries. ;)
Looks great :)
-
http://bitcoin42.com/blog/can-you-believe-its-almost-here/
We are busy bee's. Website was down for a few days which caused confusion. We'll ramp up a complete new page just for this baby. There will be four models. "Simplicity" (small one way), "Complexity" (small two way), "Visibility"(large one way), "Capacity" (large two way).
Simplicity will be ready sooner than later. No worries. ;)
Looks great :)
wow nice :)
-
I've asked marketing to come in and help...
(http://cdn2.hubspot.net/hub/53/file-27425252-jpg/superhero.jpg)
He should have a bitshares logo on his chest..
-
Is gemstone still related to BitShares?
http://gemspace.net
They moved to NXT because their technical advisor recommended it. I suspect that he held a good few NXT though personally.
So,this announcement dead too？
what a joke.
-
http://bitcoin42.com/blog/can-you-believe-its-almost-here/
We are busy bee's. Website was down for a few days which caused confusion. We'll ramp up a complete new page just for this baby. There will be four models. "Simplicity" (small one way), "Complexity" (small two way), "Visibility"(large one way), "Capacity" (large two way).
Simplicity will be ready sooner than later. No worries. ;)
Nice!
-
Find here the latest discussion:
https://bitsharestalk.org/index.php/topic,17608.0/all.html
And here our brand new shop page:
www.simplicity-kiosk.com
Presale starts now! Just keep in mind that the page is not 100% ready yet. Over the next days we will have payment options working and https ... for the time being you can just write me at pay@simplicity-kiosk.com
Best,
Alec
-
Can you provide a demonstration of the ATM?
-
Yes we're working on a proper video. The biggest problem is that the screen doesn't photograph so well especially in videos.
-
Is gemstone still related to BitShares?
http://gemspace.net
They moved to NXT because their technical advisor recommended it. I suspect that he held a good few NXT though personally.
So,this announcement dead too？
what a joke.
Wow, really what? No we didn't move to NXT, but we were put in the very difficult position of not knowing when BTS 2.0 would be launched and therefore when we would have to rewrite our entire code base and standup new infrastructure had we launched prior to now. NXT was on the table as a possible stop-gap solution, but I don't think anyone seriously advocated it for what we're doing. Bitshares has features we need that NXT doesn't. Right tool for the right job.
Now the super secret BTS 2.0 source sauce has finally spilled we can work to stand it up. First step is getting Bitshares 2.0 to actually compile and run, while trying to track down docs on the new API. Thank god we waited, because not much I'm seeing matched what was there before.
Both Gemspace & the ATM/Kiosks use Bitshares. Gemspace uses it for helping companies to use it for issuing literal shares on the blockchain and the ATM uses it for settlement.
-
So does the ATM utilize graphene or bts1.0? I'm guessing since you're still figuring out how to compile bts2.0 the latter is true. That is disappointing for several reasons. Firstly graphenes code base has been public for more than a month. For the purposes of an ATM you don't need a full or light client installed in the ATM you just need a script that connects to the websocket. And lastly if it is utilizing bts1.0 it is absolutely useless at this point. You really shouldn't be taking pre-orders until you have things better ironed out.
-
So does the ATM utilize graphene or bts1.0? I'm guessing since you're still figuring out how to compile bts2.0 the latter is true. That is disappointing for several reasons. Firstly graphenes code base has been public for more than a month. For the purposes of an ATM you don't need a full or light client installed in the ATM you just need a script that connects to the websocket. And lastly if it is utilizing bts1.0 it is absolutely useless at this point. You really shouldn't be taking pre-orders until you have things better ironed out.
It uses graphene. Getting BTS 2.0 to compile was a bit of a challenge no doubt. The instructions out there don't really explain what's needed to stand it up as a service under linux and they still reference the graphene github not the bitshares-2 github. Despite the fact they are identical right now, they may not always be. Either way ,that challenge has been overcome and I even wrote a tutorial on how to get it setup, it's posted over in the support section of these forums.
The Graphene code base may have been available for over a month, but it was a moving target and if you look at the commit log, you'll see there have been many, many revisions in that time frame. It was a moving target and you can't really architect around that. Now the API is basically frozen for awhile, it's time to get to work on that aspect of our code base. Yet if you look at the official release such as the webwallet, it's still not functioning reliably and correctly.
But at least what "should" work is defined and that's a good starting point for integration.
As for the ATMs, keep in mind that these things "support" bitshares. They are not "specifically tailored" for bitshares, but bitUSD is a potential settlement mechanism we're evaluating and I fully support. Truth is these devices can be used to vend any electronically delivered product including giftcards and other cryptos. The design is flexible enough that it doesn't matter what you're selling as long as it can be delivered via some electronic means. It's just a matter of connecting the fulfillment engine up to the retail side.
We were originally going to support the 1.x bitshares and you'll see I made a few posts about that, but once a release date was announced on 2.x it no longer made any sense to try and support 1.x. The deadline was too close and we would have had migration issues. A wait and see approach was warranted. I think we were validated on this decision, considering how many live exchanges right now still don't have 2.0 support functioning yet.
So think of this announcement this way...
We aren't taking pre-orders in the sense of "one day a product will be made".
We're not 20 something kids in our mom's basement asking for funds on kickstarter for a project that may or may not ever see the light of day.
We're not asking the bitshares community to crowdfund a project.
We're letting you know that we have a product, it's real, bitshares support is being integrated and the physical device is shipping right now.
As soon as the software upgrade is complete it will be added to the image in manufacturing and also provided as a downloadable upgrade for owners who want to sell bitassets through their ATMs.
We are now at the point where we're producing demo videos of the thing in action and getting ready for a big marketing push, once that is done the price goes back up.
In the meantime we have manufacturing capacity we're paying for. Therefore, we're taking orders and filling them in batches. You get what comes off the line when it comes of the line and since we aren't paying for marketing just yet you get a substantial discount for buying early. Once the marketing push begins on Nov 1st, the discount drops off.
Even without the discount it's still the lowest cost crypto enabled ATM/Kiosk on the market and you can buy it right now with BTS or bitUSD.
-
Ok great. I see that your machine supports one way conversion from fiat to crypto. What are your plans for bidirectional conversion? I understand that the hardware would cost more, but is it all feasible to make crypto ATMs that convert crypto to fiat? I've always thought it was interesting that one way bitcoin atms take in fiat and send crytpo, when that's not really what you expect from an ATM. The point of an ATM is to withdraw cash. I think that if you were to construct the ATM in this way it would differentiate your product from competitors and provide greater utility since it is pretty simple to acquire large volumes crypto from exchanges such as circle and coinbase but less simple to turn your crypto into cash.
While I don't think I would purchase a one-way atm that provides crypto, I would certainly purchase one that provides cash.
-
So does the ATM utilize graphene or bts1.0? I'm guessing since you're still figuring out how to compile bts2.0 the latter is true. That is disappointing for several reasons. Firstly graphenes code base has been public for more than a month. For the purposes of an ATM you don't need a full or light client installed in the ATM you just need a script that connects to the websocket. And lastly if it is utilizing bts1.0 it is absolutely useless at this point. You really shouldn't be taking pre-orders until you have things better ironed out.
Yea, clout, I hope you meant well but what you wrote wasn't well thought-out .
These guys are doing an outstanding job and we are in no position to dictate the timing of their actions.
-
So does the ATM utilize graphene or bts1.0? I'm guessing since you're still figuring out how to compile bts2.0 the latter is true. That is disappointing for several reasons. Firstly graphenes code base has been public for more than a month. For the purposes of an ATM you don't need a full or light client installed in the ATM you just need a script that connects to the websocket. And lastly if it is utilizing bts1.0 it is absolutely useless at this point. You really shouldn't be taking pre-orders until you have things better ironed out.
Yea, clout, I hope you meant well but what you wrote wasn't well thought-out .
These guys are doing an outstanding job and we are in no position to dictate the timing of their actions.
I just asked a question... There hasn't been very much information. No ones going to send $800 - $1500 to someone that they don't know for a product they don't know works.
-
Hi @clout,
We are in the CryptoATM market since early 2014 and have been alalyising the market since as early as 2011. Truth be told, right now the majority of all BTMs make their volume with Cash in Crypto out. That said, we do see a huge potential on cash out options in certain areas. But when it comes to dispensing cash to the public, things become more complicated, not only on a technical level. However, we are absolutly woring on that solution and want to deliver not only the most affordable one way ATM, but also two way ATM. You can see our goals defined here: http://simplicity-kiosk.com/index.php?route=information/information&information_id=4
Over the next couple of day we will be adding more information. We are also looking for somebody who can help us setting up a witness account and/or worker account. If anyone is interested, please PM me or write to alec@gemspace.net
Best,
Alec
So does the ATM utilize graphene or bts1.0? I'm guessing since you're still figuring out how to compile bts2.0 the latter is true. That is disappointing for several reasons. Firstly graphenes code base has been public for more than a month. For the purposes of an ATM you don't need a full or light client installed in the ATM you just need a script that connects to the websocket. And lastly if it is utilizing bts1.0 it is absolutely useless at this point. You really shouldn't be taking pre-orders until you have things better ironed out.
Yea, clout, I hope you meant well but what you wrote wasn't well thought-out .
These guys are doing an outstanding job and we are in no position to dictate the timing of their actions.
I just asked a question... There hasn't been very much information. No ones going to send $800 - $1500 to someone that they don't know for a product they don't know works.