CROSS CHAIN HOT SWAPPING
User 2 Bitcoin Address
User 1 Altcoin Address
User 2 Altcoin Address
User 1 Bitcoin Address
input X altcoin
input Y bitcoin
Recieving X altcoins via inferno
Recieving Y bitcoin via inferno
In reality X altcoins wouldnt equal y bitcoin
and you would use the sum of available coins
User 1 wants altcoin
User 2 wants bitcoin
User 2
User 1
Altcoin Blockchain
inferno network overlay network
for Altcoin
inferno network overlay network
for Bitcoin
Bitcoin Blockchain
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
SYMBOLIC HASH
input X = 1 BTC @ address Y
SYMBOLIC HASH [256-512bytes]
25% of input X = 0.25 BTC @ address Y
SYMBOLIC HASH [0-256bytes]
25% of input X = 0.25 BTC @ address Y
SYMBOLIC HASH [512-768bytes]
25% of input X = 0.25 BTC @ address Y
SYMBOLIC HASH [768-1024ytes]
25% of input X = 0.25 BTC @ address Y
Owen signing keys
SYMBOLIC HASH
INPUT = 1 BTC
P2SH redeem script
Bitcoin Blockchain
input X address Y
Owen
inferno worker
WALLET APP ANDROID
USER
OFF chain lighting
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
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
Smart Contracts
data persistence layer
normal blockchain
HOW ETHEREUM WORKS
and why its fucked
Ethereum node
problem 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 calculation
user <---response ---------- processing done
user ---command---> finite state machine
new state
user <---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 error
bundled smart contracts ontop of blockchain
chucked a data persistence layer to have a place to store contract data etc
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
Owens personal todo list
Global Owens Todo list
Worker bitch #3
Worker bitch #2
Worker bitch #1
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
stable of bitches
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:
OWEN 12311
OWEN 1111
OWEN 13123123
OWEN 123123
group text
new block
bitcoin node server
inferno labour exchange (owen)
OWEN
blockchain data directory
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)
