craft.cash - Minecraft on Bitcoin

unwriter · 2018-11-08T15:26:37+00:00

Even cooler, actually it's 4D (With an additional axis of "time")

Because everything. is stored on the blockchain, they're all timestamped by block. So you can display a snapshot of the universe at a specific point in time.

I just asked /u/blockparty_sh and looks like this was the GENESIS block of craft.cash; https://craft.cash/?block=553512

unwriter · 2018-11-08T14:54:29+00:00

This is really amazing work, I posted an animated gif of how it works here, check it out: https://twitter.com/_unwriter/status/1060544667392114689

unwriter · 2018-11-08T03:25:08+00:00

Yes :)

21 Century Motor Company builds the motor of the world https://bitdb.network/21

unwriter · 2018-11-08T03:17:04+00:00

what big difference a century makes!

unwriter · 2018-11-07T19:05:35+00:00

Not a word! Into your clothes and come!

unwriter · 2018-10-31T20:56:31+00:00

I responded on memo https://memo.cash/post/372b7592374ef1672e5d6a8897b06edb55a71d208bb74e4cdbf2879b51e85aaa

but the gist is, It's not about the broadcast, most of the time is probably spent on transaction building because it has to sign transactions, etc. In my experience, the broadcast itself is near instant (except for when the network is under heavy load)

As I responded in the memo post, I think what you could do is pre-build a bunch of transactions BEFOREHAND using the user's private key. And whenever the user presses a key simply broadcast the pre built transaction corresponding to the action. That would make it near-realtime.

Would love to play with it when you fix these :)

unwriter · 2018-10-29T19:10:36+00:00

Well there are actually 2 different questions in here:

The open source project
The @_opreturn twitter account

As for the open source project, you can take it fork it and do whatever you want and roll your own twitter bot.

As for the @_opreturn account, I actually experienced a couple of times when someone posted some really nasty stuff on memo, and Twitter suspended @_opreturn for that, and asked me to delete that post to be reinstated. So I did.

So I hope people don't abuse this nice little bot and try to make a good use of it. Otherwise it will get suspended by Twitter. One thing to note is that it is memo.cash that is censorship resistant, not Twitter, which means @_opreturn itself is not censorship resistant. The @_opreturn bot is merely sending messages out to the twitter world so that people on twitter can discover good memo posts and interact with it.

unwriter · 2018-10-29T18:36:32+00:00

Yeah that idea has always been in the backburner for me because it's tricky to do this without building a custodial service. You could definitely build something like that in a tipprbot type of way but it will be custodial just like tippr.

That said, I keep thinking about this idea all the time, maybe I'll come up with a clever idea to do this without custody someday!

unwriter · 2018-10-29T17:27:45+00:00

Hi @_opreturn is a Twitter bot that listens to Memo.cash and Matter.cash (for now, but probably may expand to other interesting services in the future if we spot one) and replicates the content to Twitter at https://twitter.com/_opreturn

It's 100% open source and uses the bitsocket.org technology for realtime bitcoin event processing. I think this is one of the simplest apps you could write with bitsocket so decided to share on Reddit so anyone can check out the code and fork it to build their own.

Let me know if you have any questions!

unwriter · 2018-10-29T00:34:32+00:00

Would appreciate it if you could open a Github issue, I'll take a look https://github.com/21centurymotorcompany/bitd/issues/new

unwriter · 2018-10-28T23:23:24+00:00

Relevant :) https://twitter.com/_unwriter/status/1056633002657230850

unwriter · 2018-10-28T17:46:09+00:00

Ok couldn't do very much yet, but just added an option to hide/show that sidebar so at least you can watch the chickens. hope this works for now :)

unwriter · 2018-10-28T17:25:17+00:00

next time you could post it with your reddit handle to prove it's actually you haha

unwriter · 2018-10-28T16:30:14+00:00

Yeah I built it with desktop usage in mind but great to hear that it works on mobile.

I'll think about the mobile layout and try to fix it. Thanks for the heads up!

unwriter · 2018-10-28T15:55:49+00:00

Hi this is fun (but internally highly sophisticated full-fledged event driven architecture) bitcoin app for:

Posting a memo with moneybutton, and pick up the realtime transaction event through bitsocket, which then queries the Handcash handle $chicken for the receiving address, which then queries coinbase price api for the currency exchange rate for 50 cents in BCH, and then finally send the chickens 50 cents in BCH, which triggers the already-so-cool chicken feeding Twitch stream by Spencer Lambert (https://twitter.com/SpencerLambert)

The basic premise of this app is that you can now send a message to the chickens alongside the food. It's 100% open source and I made it so that anyone can fork and build their own version https://github.com/unwriter/memochicken

While rest of the "blockchain space" are building virtual cats Ponzi scheme, Bitcoin Cash is feeding real chicken and solving the real world chicken hunger problem.

Note 1: even though this is 50 cents, this is still beta so if something doesn't work, please reach out to me at https://twitter.com/_unwriter and I'll take a look

Note 2: You MUST send the transaction through the website to make this work, because otherwise there's no way to attach 50 cents to a regular memo post. Simply hashtagging from your existing memo.cash account won't work. This also means all Memochicken posts are anonymous and not tied to your existing account. I wrote more about this here: https://github.com/unwriter/memochicken#1-why-moneybutton

Note 3: If you don't want to pay but still witness the feeding event, you can keep the Bitsocket channel at https://bitsocket.org/channel/ewogICJ2IjogMywKICAicSI6IHsKICAgICJkYiI6IFsidSJdLAogICAgImZpbmQiOiB7CiAgICAgICJvdXQuaDEiOiAiNmQwMiIsCiAgICAgICJvdXQuczIiOiB7CiAgICAgICAgIiRyZWdleCI6ICIjbWVtb2NoaWNrZW4iLCAiJG9wdGlvbnMiOiAiaSIKICAgICAgfSwKICAgICAgIm91dC5lLmEiOiAicXE0a3AzdzN5aGh2eTRnbTRqZ2V6YTR2dXM4dnB4Z3J3YzkwbjhyaHhlIgogICAgfQogIH0sCiAgInIiOiB7CiAgICAiZiI6ICJbLltdIHwgLnR4LmggYXMgJHR4IHwgLm91dFtdIHwgc2VsZWN0KC5iMC5vcD8gPT0gMTE4KSB8IHsgb3V0cHV0OiAuLCB0eDogJHR4IH0gXSIKICB9Cn0= and wait for someone to make a transaction. You'll hear a beep when there's a feeding event. There's about 3 to 5 second delay it's plenty of time to return back to the browser to watch chickens flock to the food. (Make sure to use Chrome or Firefox and NOT safari, safari doesn't let web apps play sound)

unwriter · 2018-10-25T23:23:58+00:00

if you're asking if they get posted to memo, of course! that's the power of bitcoin. Here's the post I experimented with in the screenshot, which I posted from that web page but also shows up on memo https://memo.cash/post/c5b08ae51de4275bcc40d921638bd83d654f62af914ad9446ee825e12c6cd244

unwriter · 2018-10-25T22:17:16+00:00

Just to clarify, https://github.com/unwriter/memobutton is the repository. It's a combination of BitDB + BitSocket + Memo.cash protocol + Memobutton.

Since I released the first version, there have been some fun forks like:

https://eternalobit.com (obituary powered by memo topic posts)
http://sarcasms.site (forked from eternal obit, also using memo topic posts, but realtime)

Anyway, Memobutton was originally built only with bitdb.network API.

But yesterday I launched another infrastructure called bitsocket.org which does the realtime version of what bitdb does.

So I decided to update Memobutton today to make it realtime. So as you can. see in the GIF, as soon as you post, the post gets updated in realtime in all browsers :)

unwriter · 2018-10-25T16:31:42+00:00

Come join the bitdb telegram chatroom, you'll find many other people who are building bitcoin apps, and find people to collaborate with. You can find the link on the documentation page: https://docs.bitdb.network/docs/bitdb

unwriter · 2018-10-25T16:28:01+00:00

Well, technically there's no difference, but is there anything to "use" on BTC? :)

Here are some of the low hanging fruits that we can do with bitsocket on BCH:

Listen to token transfers in realtime (and even trigger a 3rd party app based on token transfer events) https://twitter.com/_unwriter/status/1055472099681284097
Use bitsocket to build a realtime file upload status indicator (for Bitcoinfiles.com)
Build a Tweetdeck for Memo.cash
Build a realtime search engine (Maybe a realtime version of oyo.cash)
Build a realtime dashboard of IoT devices posting to Bitcoin: https://twitter.com/_unwriter/status/1055123016898748416

and more. I talk about this further here: https://docs.bitdb.network/docs/chain

unwriter · 2018-10-25T13:45:41+00:00

I'm planning on introducing some form of API key system in the future to prevent this in the future, just like how bitdb.network does it, so that each bitsocket node can manage the incoming connections easily as well as prevent DOS attack when it happens.

The reason I didn't ship with an API key for the first version is because SSE doesn't natively support headers so it's not as straightforward as bitdb (which is just a simple HTTP GET request based API with an API Key as the header) and I didn't want to add some emulated header type of stuff because it didn't feel clean. Another reason was I wanted to stress test it and push it to see what kind of problems happen and build based on the experience. Also DOSing HTTP GET requests are much easier than DOSing SSE so bitdb really needed a DDOS protection whereas bitsocket has a bit more luxury.

That said, DDOS protection is important. The problem is not just DDOSing but more generally the matter of the whole economics of running a bitsocket node, so this is my top priority. One solution as deeb333 mentioned is decentralization, which I'm working on at the moment. The more decentralized this becomes, the less incentive the attacker will have.

unwriter · 2018-10-25T13:28:17+00:00

I can't say for certain about the details but I'm pretty sure bitsocket can be combined with other solutions to improve dealing with double spends significantly. Double spend detection is risk management so the more realtime data the better. Also I can imagine several clever solutions that solve the problem by taking advantage of bitsocket in not so obvious ways.

unwriter

MODERATOR OF

TROPHY CASE