Fewer Dragons and More Income
If I had unlimited time and I wasn't looking after exchange students I would love to get up in the morning and work on the programs I really REALLY want to get done. Get them built, tested, and published. I'd love to get my dragons up and running with the community getting behind them and having regular battles between dragons that are training regularly based on community support. In the real world automating all of that and getting the bots ready to go takes a lot more time than I have.
So I'm changing focus until January.
I'm still here and I'm still going to get things done but I'm going to rework things a little bit. I originally wanted a whole stable of dragons to fight each other but I've quickly found that too many dragons is hard to schedule battles with and hard to keep track of what they are up to. That's from the one who came up with them and named them!
Limiting the number of dragons
In that light I'm going to limit the number of dragons in the community. Also instead of having one dragon like @ashflare.gld delegating to the !PAKX community. I'll change things up a bit. The dragon accounts will instead be powered by sub accounts which will do the financial stuff so the dragon accounts can focus on battling and giving accounts for those battles.
As an example: I started up @scifi.gld which will be delegating to the @scifimultiverse curator. I started up @ocbd.gld which will be delegating to the @ocdb curator.
Those accounts will directly support different dragons. Accounts which get rewarded in community tokens like !PAKX will support one dragon. Accounts which get only hive a different dragon. So, when @ashflare.gld decided to write about the community coin driven distributions it will be a fairer discussion. At least I hope it will be.
Getting rid of the curation trail dragons
Well, I'll change their focus. I could have a bunch of dragons supporting a bunch of communities and see what kind of return curating directly gets VS delegation. However, I already have a curator dragon @hiveabbyftp. I'll use that as my baseline for how much you can get if you do the work yourself. Also it gives me more HP available to directly support this community and its members. However, I'll also make sure to follow other communities to maximize return. Ideally I'd like to reward smaller users who delegate to the @hiveabbyftp curation account but that's going to take time to get a reliable bot ready for go for that.
Real World Investments
I'll be investing in real world investments including REIT's, Dividend Producing Stocks, Preferred Shares, Time Deposits/GIC's, and more. I'll create accounts to track their progress AND I'll funnel returns from those investments into HIVE. Or at least that is the idea.
CRO and CRO-VISA Accounts
One of the steps into the "Real World" investments will be @cro.gld and @crovisa.gld. Those accounts will track investments in the Crypto.com system. That's my primary way to get money from the FIAT to CRYPTO so I'd like to document how it can be used to create income and facilitate real world transactions.
A whole lot of reorganization.
Ideally I want to streamline things. A Lot. Right now things are disjointed and don't flow well. They are hard to follow and juggling all the transactions is challenging. I want things to flow better.
One account that holds all the rewards and is transparent on how much will be rewarded every week. One account for charitable donations and a set way to determine who gets supported. Dragons that have multiple income streams from virtual and real world investments. Setting up money flows from real world investments to HIVE and from HIVE to real world investments.
I'm not forgetting about Dragon Battles, Onboarding and Gaming
I just realize I don't have a lot of time right now and I want to make sure all the funding is in so that rewards are real, investments are setup and easy to decipher, giving, spending, and other flows are transparent and easy to write about with concrete goals.
Right now things are too nebulous so I'm hoping to fix that.
And that's today's update :)