[suspended] Cryptog's Nu data feeds - BETA

NuShares Data Feeds
#136

25MAY16 update 1

Again, very sorry for the delay. I have been stucked at work. It should not be regarded as a reason though, not to update my feeds much more frequently!
I expect I am going to be able to update my feeds much more often from now on.

  • Motion votes
    – added motion vote for dual side gateway at hitbtc by @masterOfDisaster
    – removed motion vote for dual side on a NuBot gateway in Polo by @zoro - Term 3 because it passed
    – removed motion vote for dual side NuBot gateway offered by @masterOfDisaster in Polo because it passed
    – removed motion vote for accessible liquidity - encompassing NuLagoon contract because it passed

  • Custodial grant votes
    – added NuPool 9 proposal
    – added NuLagoon custodian fee request of 15APR~12MAY16
    – added @Cybnate 's dual-side passive Pybot custodial grant vote
    – added @zoro 's back pay for nubot s gateway term 2 vote
    – added NuSafe 's payment first operating period fee request vote
    – added NuPond Term 11 custodial grant vote
    – @backpacker 's custodial grant vote for NuExplorer instance
    – removed operators fee vote of @masterOfDisaster for providing liquidity on Polo via a dual side NuBot because it passed
    – removed @backpacker s custodial grant vote for producing macosx builds because it passed

  • Parking rates
    Liquidity is getting balanced so I decided to reduce the rates but still we have plenty of nubits parked that will be unparked over the coming weeks, which is likely to decrease the buy side. That is why I decided to increase the 3 months rate.
    More generally, as long as we have not replenished the reserves via new nubits sales, we need to maintain positive rates.
    – 10% @ 3 day
    – 10% @ 6 day
    – 10% @ 11 day
    – 8% @ 23 day
    – 5% @ 1.5 month
    – 5% @ 3 months

  • Fee votes
    unchanged

1 Like
#137

31MAY16 update

  • Motion votes
    – added motion vote for muchogusto’s fund liquidity provider profitability experiment

  • Custodial grant votes
    – removed NuPool 9 vote because it passed
    – removed NuLagoon request because it passed
    – removed cybnate’s PyBot request because it passed
    – removed zoro 's backpay request because it passed
    – removed NuSage first payment request because it passed

  • Parking rates
    We are experiencing a huge lack of buy side liquidity.
    Therefore we need to increase the rates drastically.
    – 30% @ 3 day
    – 30% @ 6 day
    – 30% @ 11 day
    – 30% @ 23 day
    – 30% @ 1.5 month
    – 30% @ 3 months

  • Fee votes
    unchanged

Park Rate Voting
#138

01JUN16 update

  • Motion votes
    – added the motion vote from mod to allow spread of liquidity offered by gateways to go beyond 1%

  • Custodial grant votes
    unchanged

  • Parking rates
    unchanged

  • Fee votes
    unchanged

1 Like
#139

What a boost: in half an hour,
From 10 votes to 15 votes and:

Screenshot from 2016-06-01 11:45:51.png1272×35 5.98 KB

#140

03JUN16 update

  • Motion votes
    – added the motion vote of changing spread for passive dual-side pybot for Polo and bittrex

  • Custodial grant votes
    unchanged

  • Parking rates
    – 50% @ 3 day
    – 50% @ 6 day
    – 50% @ 11 day
    – 50% @ 23 day
    – 30% @ 1.5 month
    – 30% @ 3 month

  • Fee votes
    unchanged

#141

06JUN16 update

  • Motion votes
    unchanged

  • Custodial grant votes
    unchanged

  • Parking rates
    I have increased then based on this.

– 100% annualized @ 3 day (0.8% over the specific period)
– 100% annualized @ 6 day (1.6% over the specific period)
– 100% annualized @ 11 day (3% over the specific period)
– 100% annualized @ 23 day (6% over the specific period)
– 50% annualized @ 1.5 month (6% over the specific period)
– 30% annualized @ 3 month (7.5% over the specific period)

  • Fee votes
    unchanged
#142

08JUN16 update1

  • Motion votes
    unchanged

  • Custodial grant votes
    unchanged

  • Parking rates
    I have adjusted and increased some parking rates to encourage long term parking.
    – 0% annualized @ 3 day
    – 0% annualized @ 6 day
    – 30% annualized @ 11 day (0.9% over the specific period)
    – 50% annualized @ 23 day (3.16% over the specific period)
    – 60% annualized @ 1.5 month (7.5% over the specific period)
    – 60% annualized @ 3 month (15% over the specific period)

  • Fee votes
    unchanged

#143

09JUN16 update

  • Motion votes
    unchanged

  • Custodial grant votes
    unchanged

  • Parking rates
    I have adjusted and increased some parking rates to encourage long term parking.
    – 0% annualized @ 3 day
    – 0% annualized @ 6 day
    – 40% annualized @ 11 day (1.21% over the specific period)
    – 60% annualized @ 23 day (3.8% over the specific period)
    – 70% annualized @ 1.5 month (8.75% over the specific period)
    – 70% annualized @ 3 month (17.5% over the specific period)

  • Fee votes
    unchanged

#144

09JUN16 update

  • Motion votes
    unchanged

  • Custodial grant votes
    – added vote for second deposit custodial grant of 100m NSR

  • Parking rates
    unchanged

  • Fee votes
    unchanged

#145 
setdatafeed "https://raw.githubusercontent.com/cryptog/nu_data_feed/master/cryptog_nu_data_feed.json" "https://raw.githubusercontent.com/cryptog/nu_data_feed/master/cryptog_nu_data_feed.json.signature" SSmCygqYLTmzaQwL2i7ScryVdsdjK2hhgV

Warning: data feed was changed but the initial fetch failed: Data feed signature check failed

No GUI error when trying to pressing OK in the “Data feed…” dialogue, and debug.log appears to say it’s successful.

Updating from data feed https://raw.githubusercontent.com/cryptog/nu_data_feed/master/cryptog_nu_data_feed.json
Received 1608 bytes from data feed https://raw.githubusercontent.com/cryptog/nu_data_feed/master/cryptog_nu_data_feed.json:
{
    "custodians" : [
        {
            "address" : "BF46YvCKsppCC8eDD55FKeaWQa6nbK7BUx",
            "amount" : 806.0
        },
        {
            "address" : "BPACKiS7Q5wdishcEzabgXV8dRJJV1uXgt",
            "amount" : 600.0
        },
        {
            "address" : "Snvrc5q82wfe2NjEjaQAyStpPKseWrsNqn",
            "amount" : 100000000.0
        }
    ],
    "parkrates" : [
        {
            "unit" : "B",
            "rates" : [
                {
                    "blocks" : 2048,
                    "rate" : 0.0
                },
                {
                    "blocks" : 4096,
                    "rate" : 0.0
                },
                {
                    "blocks" : 8192,
                    "rate" : 0.0
                },
                {
                    "blocks" : 16384,
                    "rate" : 0.01246026
                },
                {
                    "blocks" : 32768,
                    "rate" : 0.03738079
                },
                {
                    "blocks" : 65536,
                    "rate" : 0.08722184
                },
                {
                    "blocks" : 131072,
                    "rate" : 0.17444368
                }
            ]
        }
    ],
    "motions" : [
        "685bcc7211db2536734042c65d78d150348a3ec5",
        "c178a7fcd6941ae8845bdd286eef3130460eaab3",
        "29d364f8677c7c955d423747fcf5005fd00f2e6b",
        "bd4d153bb5c2d8cd6013b77ad8780eabc7bae79e",
        "28ad569f5224884fc1247bd9a18bf96bf8b8f0ab"
    ],
    "fees" : {
        "B" : 0.01,
        "S" : 1.0
    }
}

Received 89 bytes from data feed https://raw.githubusercontent.com/cryptog/nu_data_feed/master/cryptog_nu_data_feed.json.signature:
H8AJFH+x3ouWDTEGCKfdsqPWDAnw97GKcNAejy7PHptkKoKFQaZsEyxpik0luPXEqp1yqmdsJ7V/jfodb35cGgU=

Vote updated from data feed

Thought I’d mention it anyway.

#146

Tks for pointing out. It happens sometimes I believe when it takes time to get updated but here the feed works fine. Can you try to modify manually one field in the votes and click “ok” in the data fields dialog box to see if it gets updated correctly?

1 Like
#147

Changing Park Rates and updating the feed again updated the vote according to the feed!

I don’t get the error anymore when adding through debug window either.

1 Like
#148

Tks for checking!

#149

18JUN16 update

  • Motion votes
    – removed Dual side gateway vote at hitbtc by mod because it passed

  • Custodial grant votes
    – removed vote for second deposit custodial grant of 100m NSR because it passed
    – removed NuPond Term 11 vote because it passed
    – removed proposal vote to run an instance of nuexplorer because it passed

  • Parking rates
    unchanged

  • Fee votes
    unchanged

#150

19JUN16 update

  • Motion votes
    – removed motion vote for 1% Maximum Spread for ALP/MLP, Above 1% Allowed for Nu Funded Liquidity Operations (e.g. Gateways) - masterOfDisaster because it passed
    – added motion vote for cryptocoiner to buy 415k NSR for 500 NBT

  • Custodial grant votes

  • Parking rates
    unchanged

  • Fee votes
    unchanged

PS: I have not removed some motions from my date feeds actually even if they got passed from NuLaw perspective in order for the nu explorer to reach the 50% SDD needed to shift the display to “passed motions”

1 Like
#151

25JUN16 update

  • Motion votes
    – added No Nu Liquidity Without a Revenue Model motion vote

  • Custodial grant votes

  • Parking rates
    – Nullified them for any period because the peg is floating right now. So basically parking rates are not working currently.

  • Fee votes
    unchanged

1 Like
#152

Experiencing some issue with the signature of my data feeds.
Will fix that within the next hours.
Sorry for the inconvenience.

#153

27JUN16 update 2

fixed

#154

30JUN16 update1

  • Motion votes
    – added Temporarily cap NBT supply with full reserve motion vote

  • Custodial grant votes

  • Parking rates
    unchanged

  • Fee votes
    unchanged

#155

Which motion specifically is that? 1118f2334d0ef45676b38ebe2daaf30a8a345a7f ?
https://daology.org/proposals/4035cbbe38c0dc28c734c2e8e4cc622a5a96dbee