TokeX

PINBALL LOGIN | LOGIN SUPPORT

PINBALL ABSTRACT:

**WEB3 MAXI WARNING** We use email addresses to manage our login.

**ORDINAL MAXI WARNING** Pinball uses a centralized server to manage "colored coins".

PINBALL.cash is the name of an "airdrop economy" aimed at "monetizing the distribution of FREE value for ALL."

The site itself is a working thesis studying "peak capitalism distributive tokenomics" & non-punitive financial lending strategies, autonomous blockchain mechanisms, lattice tokenizations for blockchain efficiency, atomic solutions for interplanetary data transfer. The pinball_protocol is a HYBRID blockchain(L1)/database(L2) solution for creating "colored coins" and managing "tokenization transactions" or "TokeX" (pronounced "tokes"), chronicling ownership through the movements of 0.00001 fractions of any RPC based cryptocurrency.

The first successful pinball_protocol TOKENIZATION TX using TRIANGLESCOIN on 2/6/022, using a hybrid L1/L2 solution for creating "digital assets" or "things". The pinball_protocol is built from Ruby On Rails(RoR) and MAZA. This "lattice" allows us to utilize the best of both forms of data storage. RoR gives us speed and gas-free processing while the blockchain creates an immutable record of our "tokenization transactions".

Because "Pinball" was originally built from a "defunct" 2014 cryptocurrency (TRIANGLESCOIN) and styled with heavy web 2 overtones, the team likens it to a venerable pinball machine. Balances are directly queried from the MAZACOIN server, thus giving users a true blockchain experience that can feel like a pinball dissapearing and returning to play as inputs become outputs and then inputs again.


CONTRACTS THROUGH CONTROLLERS:

While pinball.cash offers many functions for several coins, ALL of the features are built and tested using the MAZA blockchain. Pinball uses Ruby on Rails "MVC" architecture to create complex "gas-free" business logic while using the blockchain as a data receipt to create, trade and confirm ownerships. Because any site can implement their own version of the pinball_protocol, Pinball's architecture as a model for data decentralization may seems a bit chaotic. Every site becomes its own network while having the ability to trade data and value to other "networks" through their related cryptocurrency.

"peak capitalism", distributive tokenomics & non-punitive capital lending
Pinball.cash, as an implementation of the pinball_protocol, strives to be a modern utility for all economies looking to increase GDP by sponsoring consumers through likely, random, and autonomous distributions of value. Pinball connects active members using the CAFE where active users are rewarded daily with 1 airdrop every 3 hours while 1 user is picked every 8 minutes for an automated airdrop. There are 180 of these automated airdrops per day. Cryptocurrency inputs can be compared to pigeons because they leave and then return. The pinball economy allows any member to own a "Tesla Pigeon." Once a pinball fancier, your pigeons earn rewards up to 180x per day if they are selected to deliver the random rewards. Another example of interactive NFTS is pinball's gamified airdrop, "ROCK, PAPER, SCISSORS(RPS)". Anyone can own these assets and when members play, the images uploaded by RPS holders are viewable by game winners when they are selected at random to represent gameplay. In addition to 2 optional airdrop games (RPS & Guess the Number Behind my Back), the pinball.cash airdrop economy offers a weekly "lottery themed" gamified airdrop called the POWDERBALL. The gameplay is similar to everyone's favorite mainstream lottery but the winning algorithm is designed to give away ALL the proceeds. All entries are scored with the MOST winning ticket earning the largest payout. All tickets are ranked and the distribution is delivered in 1 TX to ALL winners! The "Golden Button" in the CAFE allows anyone to AIRDROP ALL members through one simple online form. The pinball_protocol was designed for all forms of trade, including time banks. Please see solutions for mutual aid networks.

autonomous blockchain mechanisms
Pinball uses RoR ActiveJob to scan pinball inputs and has a variety of mechanisms that monitor inputs and both increases or reduces their amount to optimize platform speed and efficiency. Pinball uses an RoR ActiveJob controller to run alongside the pinball.cash server to check for auction, raffle and event ticket sales every 5 seconds while managing platform inputs in between airdrops every 8 minutes and finalizing the POWDERBALL every 7 days. Pinball pays homage to Dune and friendly farm animals by naming this controller "THUMPER."


Meet THUMPER, the dedicated pulse of the pinball economy. Every 8 minutes THUMPER randomly selects two active wizards in the CAFE and airdrops (2 MAZA EACH) via pinball pigeons while paying their fancier for the service (3 MAZA). Anyone can keep a "MAZA TESLA PIGEON" and become a pinball fancier for 3000 MAZA in the CAFE. Every 5 seconds THUMPER scans pinball accounts and consolidates any excessive cryptocurrency inputs created by airdrops while automatically spawning "pinball pigeons" (creating new inputs) as needed. THUMPER also finalizes ADVANCED TRADING FEATURES (HIGHEST BID, WAFFLE & STADIUM TX) and particulates all POWERBALL jackpots 7 days after the first new ticket is created. THUMPER is built using Ruby on Rails ActiveJob.

lattice tokenizations for blockchain efficiency
One of the unexpected benefits of the pinall_protocol is the relative low cost per transaction. Over time, the protocol has developed a number of tools that leverage both blockchain and database while offering speed and efficiency.

escrow/exchange solutions for interplanetary exchange
Pinball completes all processing logic offchain and can confirm both "payment" and "asset delivery" in one transaction. This TX architecture offers instant confirmation via the cryptocurrency mempool.


TOKENIZATION STRATEGY:

Pinball's development team at Whalebone Intragalactic has been using "coin control" to tokenize economies in Detroit since 2014. Their focus has always been simple, LoFi, low-cost, gas-free, hype-free, FOMO-free tokenization and decentralization strategies.

After finding tfreedman's explorer, the pinball team began building RoR Controllers capable of creating dynamic, non standard, programmatic blockchain transactions. These transactions, confirmable and interpretable through RoR using 1-5 standard RPC server calls, take on new meaning inside our RoR database.

Simply put, the pinball_protocol's tokenization strategy is to issue and transfer ownership of assets through the movement of 0.00001 units of MAZA.

How Pinball creates colored coins:

THING CREATIONs (TOKENIZATION TRANSACTION) are represented by 2 ADDRESSES our RoR controllers manage "under the table".
One address receives "PAYMENT" while another controls the "signature" UNITS.
MEMBERS can specify an alternative MAZA address (not on pinball) to receive "payment".
A typical THING createrawtransaction follows this form:
[{ thing_signature_address : 0.01, pinball_faucet : 0.25, change_address: 0.xxx }]
NOTES: The THING creator's wallet balance is converted into the correct number of signature UNITS (100HOURS x 0.00001 MAZA = 0.001 MAZA), the Pinball faucet is paid 0.25 and the correct change is returned to the creator's wallet.

OWNERSHIP CREATIONs (INTERPLANETARY ESCROW) allow Pinball users to trade cryptocurrency for a tokenized asset in ONE transaction that can be confirmed instantly via the MAZA memory pool.
-Pinball verifies the collector's balance and checks for any previous OWNERSHIPS. Every collector has one "quiver" address for each THING they acquire.
-Pinball creates an OWNERSHIP transaction from a combination of inputs from both the THING's "signature_address" and its collector's funding address.
The output is as follows:
[{ quiver_address : 0.0004, pinball_faucet : 0.025, receive_address: 40, signature_address : 0.0096, change_address: 0.xxx }]
NOTES: The quiver_address receives correct amount of acquired signature UNITS from the signature_address, the pinball faucet is paid, the THING's "maker" receives exchange VALUE, "leftover" signature UNITS are returned to the signature_address, the change is returned to the "collector" and a new TXID is added to OWNERSHIP collection for "spoof" verifications.