Switch to ArdorForum

[Funding Request]

Asset name: SuperNETx2

I would like to create a SuperNET backed asset that is 1:1 convertible for SuperNET on demand. Additionally, it would receive the previously unallocated 5% SuperNET revshare. By using the 5% of assets for the missed bonus, this 5% revshare will make this asset receive double the SuperNET dividends, so when dividend valuations dominate the pricing, it will be worth 2x SuperNET. With the backing of 1 SuperNET, it is worth at least 1 SuperNET. Market price is expected to fluctuate between 1x and 2x SuperNET pricing and provides a barometer as to the market's sentiment as to how large a part of the market price is based on future dividends. If the market assessment is zero, it will trade at 1x, if the market assessment is that SuperNET dividends are the dominant valuation factor, it will trade very nearly at 2x.

This asset will not be dividended out, but rather earned. The v1 dev team is hampered by the need for real world expenses, eg. RL. So if SuperNET is to have a reliable release process, it needs to properly fund such a group. By using a SuperNETx2 asset as payment, it will reduce selling pressure on SuperNET as it is redeemable at 1x, but could be worth up to 2x, so only people who are desperately needing SuperNET to BTC/NXT would ever sell it. I expect there to be an immediate market for this, so people could just directly sell their SuperNETx2 and since the secondary market will most likely be above SuperNET price (otherwise they can just redeem).

It is a fine balance required between the decentralized community versus getting a specific product out in a timely fashion. I think the redhat using linux is a good analogy. redhat is using the output of the decentralized linux community, but it itself has to have all the normal structure of a standard organization.

The details of how the budget will be used has not been finalized. The timeframe is that it should last for 2015, also that it has the ability to allow for the decentralized community to use a tipping mechanism to allocate part of the budget. This incentivizes tip earning behavior and would be the only way people outside of the product management team is able to earn SuperNETx2.

product management members can choose to receive BTC or SuperNETx2 at CMC price for SuperNET at time of payment
I am assuming that by the time the 100 BTC runs out (or immediately!), the extra revenues for SuperNETx2 will make it the more desirable form of payment anyway.

Assuming SuperNET (or BTC) price goes up significantly, the 40K SuperNETx2 will last longer than 1 year. By the time the SuperNETx2 is fully earned, then we will hopefully have many people who are able to survive based on the dividends they are receiving.

The product management team will self-evaluate each other to make sure that everybody is providing the availability and productivity expected. The community will have the ability to suspend overall payouts in the event of, well, I think this is something that is hard to define all the possible triggers as to what is severe enough to warrant such a suspension. So, I think a simple process where anybody can post here that they are wanting to suspend the payouts to the product management team and if they get 4 committee votes, then the payouts are suspended pending review, correction, etc. Specific details on what needs to be done to be determined on a case by case basis, with myself holding some sort of tiebreaking power if there is no consensus that is achieved on the resolution requirements.

40803.05 total assets 1:1 redeemable for SuperNET
additionally 5% revshare combined with the normal SuperNET revshare to be passed through to holders
and 100 BTC allocated for short term payments

I would expect a community ratified product management team and budget to be in place before any actual disbursements are made. I have allocated the remainder of the 57 BTC discretionary funds as a bridge payment to keep things on track. The asset would be created and funded as soon as the approvals here are obtained.

This is a very important initiative and puts in place a professional management team for the product release cycle, while still retaining the decentralized nature of SuperNET. For now, getting the overall budget approved is the priority to make the compensation real. Then I suggest that the product management team can discuss the details of budgets, personnel, etc. here until there is consensus that is then ratified by the community.

I really do not want to have to get bogged down in day to day, or even week to week funds management issues. So once this is approved, I would like to have the committee approve the product management team payouts using a less formal process than 4 votes. Maybe just any committee member can be making the approval, but we honor any dissenting opinion with some civil discussions. The key to me is that I am just making a pre-approved lump sum payment, which then gets distributed as earned. Essentially I would just be providing escrow function for this and when Phasing is available, I plan to just put it all in a Phased account and then I wont even need to be involved in this part at all.

James

[Funding Request]

Please find below the details for the proposed income levels for each CPMT role. The simplest way to cover for personnel changes in different positions is to pay the income for the role performed, hence the use of multiple requests concerning the same people in some instances.

These roles have been identified and evaluated based on the activities of the last couple of months and the anticipated needs for the immediate and the short-term. As has already been mentioned, the proposed 12-week cycle is intended to both deliver on the needed sNET GUI fully-dual-mode completion and establish proper operation, management and control systems for the critical components, essential to the operation of the superNET GUI which is, to begin with, the MGW.

MGW server operators (Bitstarcoin, Bassguitaman, PNosker) - Each of these people operate one of the three MGW servers set up to provide the core multi-wallet function for the sNET GUI. They will be responsible for regularly reporting in to the MGW Supervisor/Mgmt positions on the status of their server and ensure that their server is secured and stable at all times. Where cross-server work is done, namely, where one server operator has performed work on another operator's server, the checking and maintaining of security-related codes and keys will be the responsibility of each operator for their own server. MGW Supervisor/Mgmt staff will provide for contingency fall-back in the event of a MGW server operator deviating from the required level of operation/maintenance and their operators position will be reviewed and revised if necessary.

MGW operator income per week is requested for each of the three operators to meet the equivalent of 350 Euro, with 100 Euro to be paid in BTC and 250 Euro to be paid in SNETX2 shares.

There is a fourth MGW server, the bridge node, which will be operated and maintained by Frohike and also warrants the same payment structure.

MGW/Security Management and Supervision (Vanbreuk and Frohike) - Both of these roles are essential to the need for oversight of the MGW triplet operators, as well as Vanbreuk providing for oversight of the bridge node operated by Frohike. These two roles will incorporate the implementation and operation of proper controls relevant to the functioning of live critical systems, in that once a stable MGW is achieved, arbitrary alterations and down-time of the live servers will not be permitted. These two roles will be responsible for the testing and controlled implementation of new functions and features to the MGW and related systems.

MGW/Security Management and Supervisory role income per week is requested for each of the two positions to meet the equivalent of 900 Euro, with 450 Euro to be paid in BTC and 450 Euro in SNETX2 shares.

ICAN Continuous-delivery and control infrastructure implementation and management (Frohike) - Central to all superNET project operations, particularly in terms of a commercial-level standard of critical system development, management and improvement, this structured methodology of working will create an environment capable of regularly delivering on product/technical advancements, while maintaining systemic controls to ensure the proper testing and managed implementation of proposed changes to live systems. These process will deliver broad scalability to the project management and production, allowing for unbroken progression and expansion.

ICAN Implementation and Mgmt income per week is requested at the same rate as for that of MGW/Security Management and Supervision role.

Graphical Design contractor (Eth) - Anyone who has seen a preview of the superNET v1.0b GUI will attest to the intuitive user experience being formed within Eth's initial design layout. Whilst already reimbursed for the work done for this core layout, the GUI will need further enhancement and development in order to incorporate essential sNET features and advanced services. A 12-week cycle at a rate still considerably less than market, will see all Graphic design work completed that is needed to maintain the quality and professional feel of what is intended to be the ultimate superNET client and the only client a user needs irrespective of their knowledge level. Coupled with being retained at this rate for the complete superNET GUI clients (desktop/mobile), this role will also serve to benefit ancillary areas of the project in need of occasional graphics work or design assistance.

Graphical Design contractor income per week is requested to meet the equivalent of 1800 Euro per week, payable 50/50 BTC/SNETX2

Payment per-week overview:

Bitstarcoin - EUR350 (EUR100 in BTC, EUR250 in SNETX2)
Bassguitarman - EUR350 (EUR100 in BTC, EUR250 in SNETX2)
PNosker - EUR350 (EUR100 in BTC, EUR250 in SNETX2)
Vanbreuk - EUR900 (EUR450 in BTC, EUR450 in SNETX2)
Frohike - EUR2150 (EUR1000 in BTC, EUR1150 in SNETX2)
Eth - EUR1800 (EUR900 in BTC, EUR900 in SNETX2)

All of the above people have proven backgrounds in delivery and in some cases will need to actually turn down income from RL sources in order to perform their roles successfully for superNET.

I can absolutely support and justify every cent of the proposed payment structure I have laid out for this initial 12-week cycle, a cycle which is intended to produce results and do so professionally and to high standards. Anybody who can no longer perform their required role for any reason will be expected to understand the need to replace them.

If you have any questions, feel free to ask, otherwise I would urge this be approved as soon as possible.