Developer Journal

Owen Kellogg
05/02/23

Powco has many needs so I must focus on the most core components becoming as high quality as they possibly can. Many bugs and technical debts arise from lack of long term investment in collaborative productivity especially in terms of documentation. The stag relayx module which is causing our current malaise does not yet offer any structured, auto-generated documenation whatsoever. The stag-relayx module ought to be extended with typedoc, which shall be exported and hosted at stagwallet.io and relayx.pro on the page referencing the stag-relayx module. While focus is on documenting the stag-relayx alongside patching the current bug, documentation for the interface regarding author identity protocol within all existing stag functions should be made available in a separate branch. The separate branch will be created as an auto-branch from the issue for adding author identity protocol as an option for all stag relayx functions. For each function one or more code examples shall be provided as inline documenation that typedoc may parse and display to the user on both github and the documenation site. It might be possible and desirable to use github pages to automatically host typedoc documents, specifically html pages. However it may be even more powerful to automatically host each revision of the documenation completely onchain using b protocol and the onchain.sv web browser renderer system. Most importantly typedocs shall be systematically generated and reliably hosted somewhere with stable links for long term reference.

Going further, more deeply on quality of the software it could use tests of both typescript as well as react objects and rendering. It could also benefit from release automation using semantic release, as well as further tightening of the strictness of the typescript compiler's rules. For better collaboration it shall use prettier to automatically format the code in a standard way on every git commit through a commit hook.

By creating tests for each stag function decorating the relayone wallet there arises a need to be able to mock the relayone object so that tests may be run outside the browser, in node.js and other contexts for automated testing. Furthermore both a fake stub wallet as well as a real wallet could be provided, as well as the relayone object given by relayx. When wrapping the relayx object there shall be some way to either indicate the wallet is of a different type, or simply provide an object that exactly implements the stag relayone interface. That will require creating typings for the existing relayone methods used by stag relayx and then make two more implementations. Those two implementations will be native stag loaded via wallet backup seed phrase, and an in-memory mock object that can be used for tests. It might not even be necessary to write a fake one for tests since there may be some other more desirable methods for stubbing or mocking the relayone object within those tests.

The seed-phrase-based wallet implementation shall use the same interface as relayone in typescript but implements all the wallet operations independently of relayx back end infrastructure, a capability it possesses given its direct access to the wallet seed phrase. In the near future many of these core types will be made open source by relayx and some of them can be replaced by that superior code, and the relayx typings will become more widely integrated into stag wallet core. In the mean time the core stag wallet implementation must work in both browsers and node.

Through the process of developing with typedoc one shall be able to generate documenation of relayone itself as well as possibly the back end apis that relay uses to expose indexed data to its users. Also by combining stag relay with stag wallet it can ultimately be a single module that allows for multiple back end implemenations. That way the same code can be re-used to construct software agents that run in a node actor system or that respond to events in the mempool or to messages sent directly via http as websockets. Back end applications that interact as users within the system reside in a little-explored frontier of productive value. Through stag wallet, users may use their existing relayone identities within automated apps that post, interact, and transact on their behalf. The scale of the vast quantity of possible automated interactions with reactive actors dramatically outsizes manual transactions. For example a brand may desire to ensure each of their twelve advertisements is being boosted sufficiently every day to all the right channels. Sounds like a headache! Imagine someone having to constantly manage that calculation all the time every day, and now scale that out to millions of users and a gigantic amount of human energy and time would be wasted that could otherwise be spent on boostpow. Instead a robot actor using the brand's seed phrase could monitor the boostpow network and make sure they are always all being boosted in the right quantity of difficulty every hour of every day while the promotion is on. With a bot anyone at any time can promote their own content like traditional web 2 advertising platforms via social media, but using boostpow.

Creating boostpow subscriptions can grow our ability to communicate continually by an order of magnitude, at an exponentially lower human cost because they may determine the parameters of their boostpow advertising campaign one time, and it will run automatically without intervention. The entire program to run your own boostpow advertising campaign shall be an open source program that one may run in a docker container or any supported machine. By running the docker container you will be able to create and upload new boostpow advertisements to your running docker instance. The advertisement parameters may be stored in a database or very simply in an embedded file database that can be saved to a volume or to the file system mounted from the host to the container. Either way it should be as simple as possible to first start the advert program but then also subsequently add new advertising subscriptions to the system. As the manager of an advertisement I want to be able to activate or de-activate an advertisement. I want to be able to do that either via a web app when I start it up, or via a command line interface but for the CLI I don't want to have to install anything new and would prefer to use the docker image to execute functions or even execute them on the currently running advert container process through docker exec. That would keep it all self-contained without need to access the container from any outisde networking. In fact it could start up and not even have keys set up and no data but simply sit waiting for instruction until you as the admin connect via exec bash and run the advert-cli commands required to configure your advertising bot. In that set up you do not necessarily need to ever expose your container to any ingress ports at all, increasing the security. It can be also run so that the seed phrase or hd private key are stored only in memory and ideally in a way that would be very difficult to access outside of the pre-defined parameters of the app.

The advertising app shall connect with pow.co api to get the latest or recent boostpow jobs and successful mines. Ultimately it is nearly guaranteed to increase the network hash rate reliably, if only because I myself will be using advert extensively to get the attention of the right people. Most often something I boost I would like to continue boosting indefinitely, but I inevitably forget beecause there is too much good information out there. Ideally I could give it thousands of pieces of content to boost with extremely tiny difficulty each and have those all boosted several times per day forever.

How To Invest In Boostpow

Step 1) Buy hashing machines (linux, mac, linux, etc) and plug them into your electricity socket and internet connection.

Step 2) Run the decentralized, free and open-source boostpow hashing software.

Step 3) Earn bits by competing with your hash power to help people promote useful information.

Beware!! If someone wants you to buy into their "boostpow startup" they might be attempting to create a walled garden within bitcoin and will fail.

Let the hash power be your guide.

Bonus Bits:

Use the coins you earned hashing boostpow to promote information that might help others grow the amount of bits you are earning with your hashing machines.