Difference between pages "Hardware" and "User talk:Slackjore"

From Obyte Wiki
(Difference between pages)
(added Byteduino text from tarmo888)
 
(added link to grants doc. needs article)
 
Line 1: Line 1:
−
This is a page about using Obyte with hardware devices: BIoT, Byteduino etc
 
  
−
== BIoT (Byte IoT) ==
+
==Talk==
−
=== IoT ===
+
blah blah
−
The Internet of things (IoT) is the network of devices such as vehicles, and home appliances that contain electronics, software, sensors, actuators, and connectivity which allows these things to connect, interact and exchange data.
 
  
−
The IoT involves extending Internet connectivity beyond standard devices, such as desktops, laptops, smartphones and tablets, to any range of traditionally dumb or non-internet-enabled physical devices and everyday objects. Embedded with technology, these devices can communicate and interact over the Internet, and they can be remotely monitored and controlled.<ref>https://en.wikipedia.org/wiki/Internet_of_things</ref>
 
  
−
=== BIoT ===
+
Everything below this line is Slackjore's personal editing space, future articles maybe, etc. No talk there!
−
BIoT has been funded with an Obyte grant. It allows you to manage and monitor the process of payment (using Obyte micropayments in [[Dev#Payment_channels|payment channels]]) and communication between devices by using the BIoT client on your smartphone or, for example, the onboard computer of your electric car.<ref>https://hackernoon.com/welcome-to-biot-iot-solutions-on-byteball-platform-94c4d7640f03</ref>
 
  
−
==== Example of payment per use ====
+
<hr />
−
'''Bosch-BIoT: Self-sustaining 3D Printer'''
 
−
<youtube>https://www.youtube.com/watch?v=E_cem1cl3a4</youtube>
 
  
−
The essence of this project is to create a remote 3D printing service. The user uploads a 3D model, then is shown the approximate time and cost of 3D model printing. The cost of printing is calculated by the time spent and the amount of material.<ref>https://hackernoon.com/bosch-biot-self-sustaining-3d-printing-service-f6c925b07355</ref>
+
<div style="float:right">__TOC__</div>
 +
grants: https://docs.google.com/spreadsheets/d/149vV-dc6p8rscmBA4TOCK0s12TJToBCuct0D-2SHuDQ/edit#gid=0
  
−
The video shows payment in Bosch Coins, an [[asset]] on the Obyte platform.
 
  
−
== Byteduino ==  
+
==Interoperability==
−
'''Arduino''' is an open-source hardware and software company, project and user community that designs and manufactures single-board microcontrollers and microcontroller kits for building digital devices and interactive objects that can sense and control both physically and digitally ... Arduino boards are available commercially in preassembled form or as do-it-yourself (DIY) kits.<ref>https://en.wikipedia.org/wiki/Arduino</ref>
+
Interesting article. Note the two cross-blockchain references: one of my interests is Byteball/Bitcoin interoperability to some extent despite the incompatible architectures. https://bitcoinmagazine.com/articles/history-lightning-brainstorm-beta/
  
−
'''Byteduino''' is a light implementation of Obyte for Arduino ESP8266 and ESP32 boards. It requires very little memory, working even on devices with 40 KB of memory.
+
So, what do I MEAN by Byteball/Bitcoin interoperability? Right this second it's pretty hazy to me, so let's try and work it out. It's relatively easy now -- and will get easier -- to sell one currency and buy the other, so I mean something more than that. The general idea is for users familiar with one space to be able to access the other space without the necessity of as steep a learning curve as a noob to that space would encounter. It's likely to be for one-off uses: if it's going to be a lot, the user will learn the platform proper.
  
−
This library is made to help hobbyists and professionals to implement Obyte platform into microcontrollers and build cool and original projects. Currently, this library can connect to a hub, send payments, post datafeeds, cosign transactions, and exchange messages with Obyte wallets through encrypted chat.
+
===Overlays/Shells?===
 +
There's a wide, wide gulf between a cryptofan's skillset (in the cryptospace) and a normie. Dash is trying very hard to overcome this with Evolution. Is there some way to Overlay the BB wallet with a more user-friendly interface? Is this relevant to BB/BTC interop? Two separate problems, or related? Note any overlay cannot be web-based. It's a Shell, so gonna be an app or an add-on to existing wallet(s).
  
−
=== Hardware co-signer ===
+
===Why crypto space better than Web?===
−
This is an example project. See Steemit [https://steemit.com/utopian-io/@drsensor/byteduino-create-your-own-hardware-cosigner-for-byteball-1543200264366 article].
+
Security: more certainty that what you see/pay isn't fake/hacked.  
  
−
== External links ==
+
===Example uses===
−
*[https://youtu.be/Rll5JQGNrU0 Video of BIoT system buying something]
+
====BTC space, BB injection====
−
*[https://hackernoon.com/biot-real-examples-of-work-of-our-system-20ed741c74a1 Hackernoon article of BIoT examples]
+
*Millions of merchants accept Bitcoins, especially with LN, but don't accept BB. So I want a Shell where BBUser selects a merchants shopping cart, pays in BB, and the merchant gets BTC.
−
*[https://www.youtube.com/watch?v=JN0o7xjtPhc  BIoT payment-per-use breadboard video]
 
−
*[https://biot.ws/ BIoT website]
 
  
−
*[https://www.arduinolibraries.info/libraries/byteduino Byteduino in Arduino Library]
+
*I'm more interested in BTC users being able to get easy access to the BB space, because it will boost BB. Actually, it could swamp BB, but let's assume a gradual ramping up of interest.
−
*[https://github.com/Papabyte/Byteduino Byteduino Github repo]
 
  
−
== References ==
 
−
<references />
 
  
−
[[Category:Browse]]
+
 
 +
[[Category:Personal]]

Revision as of 10:47, 5 March 2019

Talk

blah blah


Everything below this line is Slackjore's personal editing space, future articles maybe, etc. No talk there!

grants: https://docs.google.com/spreadsheets/d/149vV-dc6p8rscmBA4TOCK0s12TJToBCuct0D-2SHuDQ/edit#gid=0


Interoperability

Interesting article. Note the two cross-blockchain references: one of my interests is Byteball/Bitcoin interoperability to some extent despite the incompatible architectures. https://bitcoinmagazine.com/articles/history-lightning-brainstorm-beta/

So, what do I MEAN by Byteball/Bitcoin interoperability? Right this second it's pretty hazy to me, so let's try and work it out. It's relatively easy now -- and will get easier -- to sell one currency and buy the other, so I mean something more than that. The general idea is for users familiar with one space to be able to access the other space without the necessity of as steep a learning curve as a noob to that space would encounter. It's likely to be for one-off uses: if it's going to be a lot, the user will learn the platform proper.

Overlays/Shells?

There's a wide, wide gulf between a cryptofan's skillset (in the cryptospace) and a normie. Dash is trying very hard to overcome this with Evolution. Is there some way to Overlay the BB wallet with a more user-friendly interface? Is this relevant to BB/BTC interop? Two separate problems, or related? Note any overlay cannot be web-based. It's a Shell, so gonna be an app or an add-on to existing wallet(s).

Why crypto space better than Web?

Security: more certainty that what you see/pay isn't fake/hacked.

Example uses

BTC space, BB injection

  • Millions of merchants accept Bitcoins, especially with LN, but don't accept BB. So I want a Shell where BBUser selects a merchants shopping cart, pays in BB, and the merchant gets BTC.
  • I'm more interested in BTC users being able to get easy access to the BB space, because it will boost BB. Actually, it could swamp BB, but let's assume a gradual ramping up of interest.
Retrieved from "http://wiki.obyte.org/mediawiki/index.php?title=Hardware&oldid=1418"