Group items tagged

hardware hacking community

overviews of Open Hardware can be found on Make Magazine’s Blog, MIT Technology Review, Computerworld, O’Reilly Radar.

Lists of existing Open Hardware projects can be found on the GOpen Hardware 2009 website, on the P2P Foundation website (here and here), on Make Magazine’s Blog, Open Innovation Projects and Open Knowledge Foundation.

4 possible levels of Openness in Open Hardware projects,

by SparkFun Electronics (USA)

Open Interface

Open Design

Open Implementation

Arduino

most popular Open Hardware project

open-source electronics prototyping platform based on flexible, easy-to-use hardware and software

ommercially produced

Most of Arduino official boards are manufactured by SmartProjects in Italy.

Arduino brand name

Gravitech (USA).

starting point

Closed

ecosystem

community

mature and simple

Creative Commons license

produce

redesign

sell boards

you just have to credit the original Arduino group and use the same CC license

without paying a license fee or even ask permission

the name Arduino

is trademarked

cheap and durable enough

two different business model

sharing open hardware to sell expertise, knowledge and custom services and projects around it;

hardware is becoming a commodity

selling the hardware but trying to keep ahead of competition with better products

companies that are selling open source hardware

the open source hardware community to reach $ 1 billion by 2015

The script code is unable to manipulate any assets excepting those explicitly declared beforehand on the smart contract,

Not only can the smart contract move_funds() between these declared accounts, as its script logic dictates, but it can also stash_funds() directly inside the contract itself!

A smart contract can be activated, after which point it takes on a “life of its own”

You can also define variables in your smart contract, which persist through its entire lifetime. As the smart contract—including its internal state—continues to process over time, receipts will continue to drop into the relevant parties’ inboxes,

A signed copy of the original smart contract shows it as it was, when the parties first signed and activated it. Additionally, a server-signed, updated version of the contract comes with each receipt, showing the latest state

Once the contract expires (or is deactivated) then a finalReceipt is dropped into all relevant inboxes, after which no other receipts are possible for that smart contract.

Let’s say a party needs to DIRECTLY trigger one of the clauses on the contract. (Instead of waiting around for it to trigger automatically based on some rule.) For example, perhaps an escrow user wishes to execute a clause in order to DISPUTE THE OUTCOME, or perhaps an arbitrator wishes to activate a clause in order to RENDER A JUDGMENT. OT’s smart contracts can do precisely these sorts of things, limited only by your imagination (and my pre-alpha code.)