June-2019 Superblock
complete
Vaughn | Pixxl
complete
All proposals funded!
Vaughn | Pixxl
Other proposals that were accepted but not published to Canny:
publication-efforts —
More info: http://bit.ly/2KQRHFT
Amount: 25,000 Ø
Payments: 1
odin_special_project —
More info: https://tinyurl.com/2fcpre6
Amount: 100 Ø
Payments: 1
Vaughn | Pixxl
in progress
Vaughn | Pixxl
Merged in a post:
Proposal for Unique Viking RPG prototype
Tobinho
For Consideration - ODIN Proposal July 2019
AMOUNT:
75,000 ODIN
PAYMENTS:
1 payment of 75,000
WHO —
Toby Worth (@TobinsSpiritShelf)
WHAT —
Build a working prototype which uses ODIN.CHAT as an initial interface to issue a number of text commands in order to create a unique $ODIN Viking. Initially, there will only be a handful of commands made available to the Viking Generator via the ODIN.CHAT message interface, and we hope to expand on this in due course.
WHY —
Makes use of ODIN coins when creating and also optionally makes use of ODIN when upgrading the attributes of your Viking.
Roadmap —
Plot the overall data model and numbers. Unique Viking ID generation, and initial attributes through an ODIN burn (price to be agreed). Attribute tokens accumulation and custom application by the user. Boost command - get it working. If there’s time, more!
HOW TO VOTE —
To vote YES with all Masternodes:
mnbudgetvote many "a64d989b6798abe3fb5b0c769ce6155d84415e2aa15ecef3afd316640b62f23e" yes
To vote NO with all Masternodes:
mnbudgetvote many "a64d989b6798abe3fb5b0c769ce6155d84415e2aa15ecef3afd316640b62f23e" no
HOW TO VIEW STATUS —
getbudgetinfo "ODIN-Game-POC"
—
ADDITIONAL DETAILS —
These are the priority commands we want to have as a minimum:
create [VikingName]
As long as the user has over 500 (for example) ODIN in their ODIN.CHAT wallet, they will be able to create a Viking by issuing this command. The game server will then automatically use 500 ODIN coins, burn them, then return the user with a ‘proof of burn’ which will indefinitely identify this unique Viking. This Viking will belong to the user, and the plan is to enable these Vikings to be tradeable in future versions.
When the unique VikingID is returned to the user, in this prototype, the Viking will have a data set of properties that can be customized and upgraded over time.
attributes (show statistix)
This will output the attributes of your Viking. These are attributes that will affect your Viking in future gamification features which will be worked on in a separate phase of development.
boost [VikingName]
The attributes can be manually increased over time, and you gain attribute tokens as your Viking increase in age. You can only have one attribute token available for your Viking, at which point the user will need to apply them before another can be ‘earned’.
Additional attribute tokens can be created for your Viking by using the ‘boost’ command to use, say, 50 ODIN coins which are burned, creating an instantly usable attributes token.
Future wishlist
Ace ideas, but unlikely in this phase of development...
Buying/trading items and other features. Vikings will be tradeable. Vikings will be able to be upgraded via equipment purchases, attribute changes over time via quests, aging, interactions with other Vikings, breeding, etc. Vikings have RPG elements, so make Odin ‘sticky’. Vikings are cool and fun and everyone will want one.
The various attributes will distinguish the Vikings, which can in future be generated as SVG characters, so they can be rendered at any size in many scenarios: e.g. icons, avatars, swag, game-sprites (via conversion to context-optimal formats).
Include weapon chests, wardrobes, quests, Viking selector (village) and more.
Vaughn | Pixxl
Merged in a post:
General Dev Fund
m
mrblister
This proposal is for using up the remaining ODIN in the June 2019 superblock. This amounts to around 8000 ODIN.
A secondary goal is to test what happens to when the total amount requested by all proposals exceeds the amount available in the superblock. To test this, my proposal will be asking for 9000 ODIN.
If this proposal is successful, I will hold onto the received ODIN until a more formalized procedure is established for making use of "leftover" ODIN in a superblock. Most likely, this will consist of transferring the ODIN to a general development fund that is held in a multisig address.