passing transaction linking data
recieving X altcoins via inferno
Owen writes his shit down,
multisig 2of3 hash
user owns 1 key for 2 of 3 multisig to redeem this input not enough to use coins timelocked to return to USER if time runs out
linked symbolic hash to input on chain for context
SYMBOLIC HASH passed from owen back to WALLET APP
lists interest in performing crypto swap Y bitcoin now available for hot swap
bitches where you at
owen mounted to blockchain data directory
hotswap address
recieving Y bitcoin via inferno
hotswap address
Mutex lock 50% for 1 key 100% for 2 keys
block being written to disk
blockchain on bitcoin server
inferno on bitcoin server
Owen abstracts away p2sh to new symbolic hash for use offchain symbolic hash maps to p2sh 1 to 1 any hash should do, pref 1024 bytes in total so most cryptocurrency denominations can symoblically map 10 to 1 symbolic hash = sha512 * 2
if X altcoins = Y bitcoin swap
supply 2 keys
start lighting bitcoin begin multisig 2of3 tran supply 1 priv key sign tran for input X at address Y
transaction signed, no boradcast no sendto address yet
Transaction finalized Y input to User 2 Bitcoin Address via inferno and via inferno > inferno hotswap
SHA512 * 2 symbolic hash 1024 bytes parceled into 4 parts 256 bytes each and linked output at address y for context
Owen provides Mappping 1 to 1
owen orders his stable to execute this smart contract right now bitches
lists interest in performing crypto swap X altcoins now available for hot swaps
2 of 3 keys necessary
SYMBOLIC HASH passed back to user to parcel and pass out
owns 2 of 3 sigs to execute send waiting on sendto address pushing timelock out of range to ensure it stays valid
transaction finalzied X input to User 1 Altcoin Address via Inferno and via inferno > inferno hotswap

NEW BLOCK

HOW NETWORK WORKS
*distributed labour exchange owen imagined as a pimp working his stable of worker bitches & keeping in contact with his other pimpin brothers (all named owen)

blockchain data directory

inferno labour exchange (owen)

OWEN

bitcoin node server

new block

group text

OWEN 123123

OWEN 13123123

OWEN 1111

OWEN 12311

so when new block arrives, owen sends a group text to all his mates also named owen, saying: bitch we got to get the bitches working, they divide the new blocks scripts/smart contracts amoungst themselves then each owen will call up his stable of worker bitches, and divide the workload equally among each of his bitches. when each bitch is done, they come back with the reciept owen checks that no dumb bitches are trying to jack his trade and then he fires off a msg to his bois with the msg:script numbx fucking crushed it, NEXT. before he moves onto next script like a good pimp, he makes a note of the reciepts from the script and writes that shit down:

stable of bitches

Worker bitch #1

r

Workers are sourced from frontend wallet application with built in inferno worker node (inferno.apk) FOR FREE MOTHERFUCKERsince workers are freely contributed by users of the wallet their use as workers is restricted. so only available when certain possibly user set conditions are met ie:wifi availablebattery at x%phone plugged intime is after X before Y

Worker bitch #2

Worker bitch #3

Global Owens Todo list

Owens personal todo list

new block being added to the server bitcoin data directory. mounted over/underneith the same directory is the labour exchange his name is owen, he a pimp

HOW ETHEREUM WORKS
and why its fucked

r

Ethereum nodeproblem 1) node is monolithic (its all 1 thing). When executing a contract, this is executed on all nodes, which is super dumb if you consider that the script need only be executed on a single server, but on eth its executed on all thousands of nodes.cost of running smart contracts will only exponentially increase with network expanse till scaling wall is hit.Problem 2) bundling together makes etherum turing complete as opposed to a finite state machine like bitcoin and other alts.turing complete = normal computer (for every input there are possibly multiple outputs ) user ---> command ----- > turing machine processing ------> sets variables processing ------ > write to disk/memory processing --------> perform calculationuser <---response ---------- processing done user ---command---> finite state machine new stateuser <---response--- finite state machine finite state machine = generalized computer (for every 1 input there is 1 output (every input and output is known, there is no way for the machine to fuck up the execution of an command, all error = human errorbundled smart contracts ontop of blockchainchucked a data persistence layer to have a place to store contract data etc

normal blockchain

data persistence layer

Smart Contracts

Ethereum node

problem 1
all contracts executed on all running nodes unnecessarily
blockchain is distributed on nodes to distribute trust.
execution of contracts/scripts on node server binds 2 services that shouldnt be bound together
cost of running smart contracts will only exponentially increase with network expanse till scaling wall is hit.

Problem 2
bundling together makes etherum turing complete as opposed to a finite state machine like bitcoin and other alts.
turing complete = normal computer (for every input there are possibly multiple outputs )

user ---> command ----- > turing machine
processing ------> sets variables
processing ------ > write to disk/memory
processing --------> perform calculation
user <---response ----- processing done

processing = potential unknown/unhandled/unhandleable error causing contract failure

when working with finanical instruments, avoid at all times the possibility of failure when executing a transaction.


Finite state machine = for every 1 input there is only 1 output
user ---command---> finite state machine
new state
user <---response--- finite state machine

any fuckup = human error

user --- stupid command ---> bitcoind
bitcoind * thinks to itself, fucking tourists
user <----bitch ur shits wack bitcoind

r

Ethereum nodeproblem 1) node is monolithic (its all 1 thing). When executing a contract, this is executed on all nodes, which is super dumb if you consider that the script need only be executed on a single server, but on eth its executed on all thousands of nodes.cost of running smart contracts will only exponentially increase with network expanse till scaling wall is hit.Problem 2) bundling together makes etherum turing complete as opposed to a finite state machine like bitcoin and other alts.turing complete = normal computer (for every input there are possibly multiple outputs ) user ---> command ----- > turing machine processing ------> sets variables processing ------ > write to disk/memory processing --------> perform calculationuser <---response ---------- processing done user ---command---> finite state machine new stateuser <---response--- finite state machine finite state machine = generalized computer (for every 1 input there is 1 output (every input and output is known, there is no way for the machine to fuck up the execution of an command, all error = human errorbundled smart contracts ontop of blockchainchucked a data persistence layer to have a place to store contract data etc

Workers are sourced from frontend wallet application with built in inferno worker node (inferno.apk) FOR FREE MOTHERFUCKER



since workers are freely contributed by users of the wallet their use as workers is restricted. so only available when certain possibly user set conditions are met ie:

wifi available

battery at x%

phone plugged in

time is after X before Y

OFF chain lighting

USER

WALLET APP ANDROID

inferno worker

Owen

Bitcoin Blockchain

input X address Y

P2SH redeem script

INPUT = 1 BTC

SYMBOLIC HASH

Owen signing keys

SYMBOLIC HASH
input X = 1 BTC @ address Y

SYMBOLIC HASH [768-1024ytes]
25% of input X = 0.25 BTC @ address Y

SYMBOLIC HASH [512-768bytes]
25% of input X = 0.25 BTC @ address Y

SYMBOLIC HASH [0-256bytes]
25% of input X = 0.25 BTC @ address Y

SYMBOLIC HASH [256-512bytes]
25% of input X = 0.25 BTC @ address Y

Workers are user contributed, with installation of Wallet application.
Wallet app servces as both part time worker node (user set conditions like wifi on, plugged in, battery @ 100% etc) & interface with inferno network

Bitcoin Blockchain

inferno network overlay network
for Bitcoin

inferno network overlay network
for Altcoin

Altcoin Blockchain

User 1

User 2

User 1 wants altcoin
User 2 wants bitcoin

In reality X altcoins wouldnt equal y bitcoin
and you would use the sum of available coins

Recieving Y bitcoin via inferno

Recieving X altcoins via inferno

input Y bitcoin

input X altcoin

User 1 Bitcoin Address

User 2 Altcoin Address

User 1 Altcoin Address

User 2 Bitcoin Address

CROSS CHAIN HOT SWAPPING