SPK - SPK DAO Funding and Updates

in #dao5 months ago (edited)

Status for March

Over 3000 accounts have claimed their March Tokens on the SPK Claim Chain. This includes quite a few of the largest accounts representing ~72M Hive and Hive Power. If you haven't claimed your tokens yet please go to spk.dlux.io or SPK Wallet @ dlux and claim before the end of the month UTC.

New UI Incoming

This presents a bit of a problem for the claim chain. The stated goals of establishing a DAO with the unclaimed tokens will upset the balance of power when more than 60% of the tokens are unclaimed. To that end we're only going to move around 15% of what has been claimed into our DAO account.

We put together some code that will claim a consensus determined (15% default) amount of claimed tokens and move them. There are also some new voting mechanisms for our node runners. Once more of the network is established this voting will move to the SPK token holders as it's planned to be the governance token for the SPK network. I'm in contact with just about all the node runners so if you want to set a higher or lower vote amount let me know; we are hard at work making UI for these changes though.

Speaking of UI. Both interfaces have been getting vast amount of development attention from @psorigins and @markegiles Check out the links above.

Technical Updates | Code Review

Now that most of the release fires have been extinguished we're hoping to do a more thoughtful review process for new features. Version 1.0.7 has the following changes.

  • Fixed release(txid) to wait for promises (order canceling)
  • Adust elmerlin balance by 9566.250 for release error in block 63014889
  • Adjust MSHeld Balance by 56 HIVE due to 1.0.4 errors
  • Added a non-claim to DAO routine
  • Added voting for DAO routine
  • Fixed Account Update
  • Added partial fill tracking on buy orders

New UI Incomming

Release - order cancel routine
  • /processing_routes/dex.js
    • dex_clear removed for loop with promise stacking
non-claim dao funding
  • /processing_routes/send.js
    newClaim = 0
            if(dao.m != json.timestamp.split('-')[1] && (json.timestamp.split('-')[0] == '2022' || json.timestamp.split('-')[0] == '2023') && parseInt(json.timestamp.split('-')[1]) < 4){
                dao.m = json.timestamp.split('-')[1] //set month
                newClaim = parseInt((supply - dao.ct) * (dao.v/10000))//only distribute based on new supply
                dao[json.timestamp.split('-')[1]] = newClaim //set claim reciept by month
                dao.t += newClaim //add to total
                dao.ct = supply + newClaim //track the current supply so new tokens only get issued off claims
                ops.push({ type: 'put', path: ['balances', 'rd'], data: parseInt(rdbal + newClaim) }); //dao account
                ops.push({ type: 'put', path: ['stats', 'daoclaim'], data: dao }); //this obect
                ops.push({ type: 'put', path: ['stats', 'tokenSupply'], data: supply + newClaim }); //update supply
// mints new tokens on the first claim of each additional month
if(!newClaim)ops.push({ type: 'put', path: ['stats', 'tokenSupply'], data: parseInt(supply + trak.s) });
                    else {
                        ops.push({ type: 'put', path: ['stats', 'tokenSupply'], data: parseInt(supply + trak.s + newClaim) }); //update supply with new claim
// further adjusts token supply if the claim op was a success
  • /processing_routes/nodes.js
var dv = parseInt(json.ds) || 0 //dao vote 10000 = 100.00% / 1 = 0.01%
        //the portion of the claim that will be put into the chains DAO. Recommend 10-15%
        if (dv < 0) {
            dv = 1500
        if (dv > 10000) {
            dv = 1500
// already finding the issue here: json.ds should be json.dv

Votes get counted here:

  • /dao.js
var newOwners = {}, dexfeea = 0, dexfeed = 1, dexmaxa = 0, dexslopea = 0, dexmaxd = 1, dexsloped = 1, dva = 0, dvd = 1
                for (var node in mnode) { //and pay them
                    const gbal = gov[node] || 0
                    const dvvote = typeof mnode[node].dv != 'number' ? 1500 : mnode[node].dv
                    dva += parseInt(wins * gbal * dvvote);
                    dvd += parseInt(wins * gbal * 10000);
            stats.daoclaim.v = parseInt(dva / dvd); //stored here
Partials Tracking
  • /processing_rooutes/dex.js
                var partial = {
                                coin: thistarget,
                                token: remaining + thisfee
                                next.partial[`${json.transaction_id}`] = partial
                            } else {
                                next.partial = {
                                    [`${json.transaction_id}`]: partial
Account Update

Wasn't pointing to the correct transaction signer. This has been worked with several minor fixes. During testing this seemed to work, but live has had slightly less than phenomenal results. Any updates here will include the above ds => dv fix in version 1.0.8 but I expect at least a day to work through this.


Good job. 1 year from now we see the true impact.

I thought that working on a web 3.0 with JS would be very difficult but with what I have just seen it is not, apart from adding comments to indicate to others that it does certain lines of code

Congratulations, @theguruasia You Successfully Shared 0.200 WINEX With @disregardfiat.
You Earned 0.200 WINEX As Curation Reward.
You Utilized 2/3 Successful Calls.


Contact Us : WINEX Token Discord Channel
WINEX Current Market Price : 0.300

Swap Your Hive <=> Swap.Hive With Industry Lowest Fee (0.1%) : Click This Link
Read Latest Updates Or Contact Us

It's a big one you are doing
A big kudos to you 😇😇

Your website doesn't work on mobile. Why not add HiveAuth support?

We will. We love options.

Cool. Looking forward to using it.
Feel free to contact me if you need help.

@disregardfiat! The Hive.Pizza team manually curated this post.

You can now send $PIZZA tips in Discord via tip.cc!

I have claimed some eheheh fun fun

Congratulations @disregardfiat! Your post has been a top performer on the Hive blockchain and you have been rewarded with the following badge:

Post with the highest payout of the day.

You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP

Check out the last post from @hivebuzz:

Hive Power Up Month - Feedback from February day 25
Support the HiveBuzz project. Vote for our proposal!

Nice content.. great