Bring up to parity with the top row of screens on this figma board:

https://www.figma.com/file/cxOUHfMZSmuR9zBMfhJtec/Break-Solana-Game?node-id=8%3A302

1. When game is finished I can see "Try again" button
2. Clicking on the button, I want to see /game screen

5k concurrent users
15k in one hour
100k in one day

Problem

Break is creating too many accounts. See more details here: #108

Proposed Changes

This captures the client side of the changes:

• Change from program subscription to account subscription
• Inspect account data to determine tx success

1. Clicking on "Build on Solana" button, I want to be redirected to "solana.com/developers"

1. Popovers are available "Stats after game" screen
2. Popover should be displayed hovering transaction
3. Information on Popover:
   a. Lamports
   b. Signature
   c. Transaction time

Problem

If apps do not bind to the provided PORT, Heroku will attempt to restart a few times until it marks it as crashed.

Proposed Solution

• Always bind to the port
• Add network failure UI state to the client app

1. Number of created transactions from all clients should be collected an send to BE every second.
2. Backend should sum up all transactions created for 5 seconds.
   a. result should be divided by 5 to get TPS
3. FE should display TPS number.
   a. TPS number should refreshed every 5 seconds

Exists on /stats

1. After the game is finished, stats should be displayed:
   Total amount of transactions
   #% of Solana capability used (Formula: #of transaction/50000)
2. "Try again" button - display "Start the game screen"
3. Message after game finished: "Well, perhaps if you invited a fem more friends...
   With transactions in 15 seconds you took up of our blockchain's network capabilities. If you invited couple more people our decentralized database would start to slow down.
   You can review every transaction with stats on confirmation and signatures hovering it."

Yes they are technically different, so it's like that we're totally wrong. But it would be a bit misleading.

Maybe just use block time in the results, like the landing view to be consistent?

Problem

Each new deploy of the break app creates a new program with a random pubkey. It would be nice if the program id was a vanity address and was always the same because these program instructions will be inspected on the explorer.

1. Page should exist on break.solana.com/game
2. Name for Browser tab: "Brake Solana"
3. Browser tab should have Solana logo as favicon.
4. Solana logo should exist on the screen
5. Countdown clock should exist on the screen. It is frozen on 15 seconds, until game is started
6. "BEGIN" button should exist on the screen. Clickin on it - game begins.

URL example:

https://explorer.solana.com/transactions/3tsR8c47jBwcSauhfgwxyHk6x462k72tyT59ke4gn1wh2wXxiEbwNJPJ8VNe1kjqNAh1WtqSYYozV6sktmggz47C

https://www.figma.com/file/cxOUHfMZSmuR9zBMfhJtec/Break-Solana-Game?node-id=8%3A302

Note copy changes

If you load https://break-solana-staging.herokuapp.com/results directly, either by pasting into the address bar or reloading the page after playing a round, you can start a new round without hitting "Play again", but the timer never starts.

1. After game is finished, I want to see 'Share on Facebook" button
2. Clikcking on the button, I want to see facebook website with prefilled message.

On the /stats screen I want to see:

1. of transactions confirmed for last 15 secinds

2. of transactions confirmed for last 24h

Maybe we can add a timer from time 0 when a user starts creating transactions? Or change up the wording

Design: https://www.figma.com/file/fStWgnFuDjGWx5W2KDppDs/Break-Solana?node-id=227%3A682

Solana logo looks low res on iOS 13 Firefox, Safari, and Chrome

I breaked a little, devnet, and got some red boxes:

, which showed

but when I viewed in explorer the transaction was all good:

We'll need to store:

Time completed
Username
Email (make a field for this)
Referrer ID (if there was one, from the URL that created the session)

For iPhone X users, the "Send Transaction" button is rendered off screen. Is it possible to have users send a transaction by tapping anywhere on the screen during the 15 seconds (or just on the transaction grid)?

Problem

Break transactions create a new account for each transaction and these accounts bloat the ledger

Proposed changes

Use BPF instructions!

• Client subscribes to account that it receives from the server
• Client encodes an id in program ix data
• Program modifies account data based on ix data id
• Client checks account data to determine which ids were processed

Problem

Each transaction creates a rent exempt account but creating rent exempt accounts is not necessary.

Proposed Changes

Only transfer enough rent to cover a single epoch.

Problem

1000's of blockhash polls every few seconds could put extra strain on the RPC node

Proposed Changes

Poll for blockhash in the server and notify clients of latest

Problem

We want to show users that they're not alone when playing Break by showing the number of concurrent players.

Proposed Changes

The break server tracks websocket clients, broadcast the client count periodically

Otherwise, it's a bit solitaire-like. :)

Also, some kind of rankings by the transaction count would be nice to have. :)

Break Solana should be playable on , mobile devices and tablets.

1. During the game - every click should create a square on the screen.
2. If the amount of squares is more, than fits the screen - scroll should appear
   a. When new row of squares is created - scrlollable area should scroll for 1 row.
3. "Total amount of transaction" should increment by 1 after every click

Problem

Want to run break on a testnet which doesn't have airdrops enabled

Proposed Solution

Detect PAYER_KEY env var and use that to fund account supply when available

1. During the game, sqaures also should be created pressing keyboard
2. Must be unique from the last key pressed, to avoid spamming by holding down a key

1. After game is finished, I want to see 'Share on twitter" button
2. Clikcking on the button, I want to see Twitter website with prefilled message.

Work the game into the CrowdIn system and hand to Austin to get translations done

Problem

Break client transactions create program accounts, and those transactions can be easily verified by subscribing to the program using the RPC pub sub API. If all break clients create accounts for the same program, the fan out of program subscription notifications is going to overwhelm the RPC server as well the clients themselves.

Napkin math: 1000 users * 15 tps = 15,000 tps => 15,000 notifications * 1000 users => 15M websocket messages per second. Each user getting 15k messages per second.

Proposed Change

Sharding!

1. Create a few hundred programs on the cluster ahead of time
2. Give the same programId to a few clients before rotating to the next programId

Problem

TPS updates are too choppy because they are calculated with a short time window

Proposed Changes

Use a rolling time window for TPS calculation so that TPS updates are smooth

1. Break solana page should exist on "break.solana.com"

2. layouts should be based image, attached to this story.

3. "Read how it works" button should exist on this screen. Clicking on the button - link should be opened in new browser tab. Link: https://solana.com/category/blog/

4. Solona logo should exist, clickin on the logo - open Solana.com page in new browser tab.

5. Solana static image should exist on this screen. This image can be animated in terms of future tasks.

6. "Play the game" button should exsit on this screen. Clicking on the button - Start/break screen should be displayed

Problem

We want to track the full impact of the break game on the cluster over time

Proposed Changes

• Create break program config account
• Add increment day count instruction
• Profit

If short on time:

• Add Redis Heroku addon
• Track sent transactions in the server and increment a date redis key
• Periodically broadcast daily transactions

Problem

When the RPC server restarts, it binds to a new random TPU udp port. The break server is oblivious to that and doesn't realize it's sending transactions into the void when this happens.

Proposed Changes

Detect RPC restarts or periodically query cluster info to make sure tpu info is up to date

Problem

We want to show users how fast confirmation times are on Solana

Proposed Changes

• Stream confirmation times and calculate a rolling median

Message:
"Currently, all players online are creating TPS, which means they are using % of Solana capacity.

You can join us and try to break Solana: https://break.solana.com/game"

https://www.figma.com/file/cxOUHfMZSmuR9zBMfhJtec/Break-Solana-Game?node-id=8%3A302

Referral link is generated at the 15 second endgame screen
Sessions started from a link with a referral ID keeps record of the referrer

https://drive.google.com/file/d/1aVKxV9Yk0P_4FBLw4-Ey2tR1v5YZbKJY/view?usp=sharing

See behavior above, maybe at a 5s timer at the top stating that you can take a breather?

% of Solana Capacity used: (x/50000)*100
x- number of transaction generated by all users online for 1 second.

Problem

This is not a correct way to calculate transaction confirmation time.

            const t1 = performance.now();
            const response = await this.connection.sendTransaction(transaction, this.keypair);
            const t2 = performance.now();

All this is doing is broadcasting a transaction to the network. Next, the network sends the transaction to the leader node who will then process the transaction and eventually produce a block with the results of this transaction (if it succeeds).

Proposed Solution

Make use of https://solana-labs.github.io/solana-web3.js/function/index.html#static-function-sendAndConfirmRecentTransaction or https://solana-labs.github.io/solana-web3.js/class/src/connection.js~Connection.html#instance-method-confirmTransaction to get the correct transaction confirmation time