nb. check to see whether the contract owner (admin role) is used in Bee Make PR to add events to Redistribution Contract & merge. i. add roundnumber to the claim/commit/reveal events https://github.com/ethersphere/storage-incentives/issues/131 ii. emit validChunkCount during claim https://github.com/ethersphere/storage-incentives/issues/130 iii. emit anchor selection on first reveal https://github.com/ethersphere/storage-incentives/issues/129 Deploy new redistribution contract to Goerli and integrate it with the current contracts. Refine and check this process. i. deploy new redistribution and link to existing contracts ii. pause old redistribution contract. iii. set the redistibutor role to the redistribution contract on the staking and postage contracts

1-8 already done Reserve depth vs storage depth (redo) Postage Stamp Priority, Reserve capacity Depths **from the perspective of a node bmt there is a:reserve depth: log(batch_volume) storage depth: the lowest PO st a node can and is able to sync the full chunks for that PO and the PO above that has more chunks than it is able to sync kademlia depth: the highest PO st there are at least 4 nodes including you within that proximity order Neighbourhood redundancy

Overview This document seeks to explore the process of prototyping and then publicising network intel and agreggated stats. We begin by identifying datas pertinent to the Research Dept's ability to survey the network in order to gain the visibility needed to ensure the games are playing out as expected, and to monitor for nefarious, unusual or inconsistent activities so that the protocol can be improved and patched in order to prevent such circumvention of desired conventions. More Data We Need What are the anchors for missed rounds, ask janos to add them but with no data, can we even find these out? maybe we need to update the contract first Prototype Ideas for stats dashboard add to price model graph, overlay, how many nodes are playing, what is the batch volume

https://www.waterandmusic.com/ https://hifilabs.co/welcome https://alpha.musicos.xyz/ https://neume.network/posts/hello-world/

Definition of depths physical depth is the highest PO that gives you a sufficently large neighbourhood consisting of at least four nodes, this guides who you are obliged to connect to (kademila full connectivity neightbourhood) storage depth is the shallowest PO such that the all of the chunks in that bin or closer still fit in the reserve, determines your storage lottery participation and sampling neighbourhood depth is the somewhere in between and determines who we want to seek out for full connectivity and reserve capacity Pullsyncing strategy when interacting with storage incentives find the R-1 nodes closet to your overlay address the PO of the furthest out of which will be your physical depth, connect fully to them and set your neighbourhood depth and storage depth to be this depth start pull syncing based on your neighbourhood depth until you have finished syncing all with all peers within your neighbourhood depth

Rise of the Bee II : Wargames Prize 100,000 BZZ? Abstract Pull together the community and test storage incentives by running a Wargame with fake data and a fake token. The Wargame will be run on XDai with fake tokens to test in a realistic staging environment. Outcomes Test situations that may cause data loss by pulling levers on a special token contracts, price oracle contracts, so that we can make things happen that we cannot cause without too much destruction or do not want to happen on mainnet.

Process Issue lifecycle Issue is raised Issue is refined Remediation is prescribed Issue is assigned Fix is actioned and PR raised 2x Code reviews + 1x QA on testnet Pull request is merged and issue closed

src/App/App.js - entry point to GetLogin. Here is info about routes and allowed domains where the GetLogin can be available public/api/last.js - the script for external apps which use GetLogin API. In the script is implemented a communication protocol between 3rd party app and GetLogin via postMessage. This script embeds an iframe in the 3rd party app using the GetLogin Plugin scripts. src/Plugin/* - embedded scripts via iframe for 3rd party apps. All blockchain requests (read, write) are proxied via these scripts. Also these scripts check app urls and contracts when GetLogin used. src/Authorize/Authorize.js - page for authorization 3rd party app. Scenarios when page used:

--- tags: archive --- # OBSOLETE !!! - MOVED TO https://hackmd.io/@crtahlin/HkCSUt4YH NOTE: @significance - might you "unpublish" this version? I think it is quite public # Epic - Fairdrop stability TODO: please: - [ ] **add your name next to story** - [ ] check if story really 2-3 days (if longer than one sprint, split) - [ ] assign priority (write S1 next to it if for first sprint) - [ ] the user stories that you copied to github use strikethrough ~~like this~~ since they will no longer b