/Motion for Patching NuExplorer for new Currencies Feb-18
Last active Mar 7, 2018
| ------------------------------------------------------------------------------------------------------------------------------- | |
| The blockchain explorer hosted at https://nuexplorer.ddns.net doesn't support the recent release of new currencies | |
| and the current code base is not very resilient. As a result of that the explorer is sometimes a couple of days behind | |
| and requires manual interventions beyond just restarting services. The new custodial grants are displayed incorrectly. | |
| This motion proposes to make some fixes without overhauling the base code to extent the lifespan of this explorer. | |
| @Cybnate will be the custodian of the funds which will only be released in full after the work has been delivered. | |
| The work will be completed by @2undroid at a cost of no more than 1,200 US-NBT. The custodial fee will be 50 US-NBT. | |
| An upfront payment of up to 33% of the estimated total may be agreed between @Cybnate and @2undroid. | |
| The following requirements will be met on delivery: | |
| - The explore status page will show information about the new currencies, in particular market price (in US$) and marketcap | |
| - Grants for the new currencies will be gracefully handled prohibiting the explorer to stop processing | |
| - Grants for EU-NBT, CH-NBT, X-NBT, JP-NBT and KR-NBT will be recognised as such on the 'votes' and 'votes/success' pages for grants. | |
| The work meeting the above requirements will be delivered within 8 weeks after this motion has passed. | |
| The NuShareholders pledge to transfer the funds to a custodial NBT address published by @Cybnate in the public forum | |
| within 3 days of the motion passing. | |
| ------------------------------------------------------------------------------------------------------------------------------- | |
| <end of motion> | |
| Please add the following in your client to support this motiont: | |
| 42145c5683b7aac2cef80d3b9dcec7dcf72a0425 | |
| The blockchain explorer hosted at https://nuexplorer.ddns.net doesn't support the recent release of new currencies | |
| and the current code base is not very resilient. As a result of that the explorer is sometimes a couple of days behind | |
| and requires manual interventions beyond just restarting services. The new custodial grants are displayed incorrectly. | |
| This motion proposes to make some fixes without overhauling the base code to extent the lifespan of this explorer. | |
| @Cybnate will be the custodian of the funds which will only be released in full after the work has been delivered. | |
| The work will be completed by @2undroid at a cost of no more than 1,200 US-NBT. The custodial fee will be 50 US-NBT. | |
| An upfront payment of up to 33% of the estimated total may be agreed between @Cybnate and @2undroid. | |
| The following requirements will be met on delivery: | |
| - The explore status page will show information about the new currencies, in particular market price (in US$) and marketcap | |
| - Grants for the new currencies will be gracefully handled prohibiting the explorer to stop processing | |
| - Grants for EU-NBT, CH-NBT and X-NBT will be recognised as such on the 'votes' and 'votes/success' pages for grants. | |
| The work meeting the above requirements will be delivered within 8 weeks after this motion has passed. | |
| The NuShareholders pledge to transfer the funds to a custodial NBT address published by @Cybnate in the public forum | |
| within 3 days of the motion passing. | |
| ------------------------------------------------------------------------------------------------------------------------------- | |
| ------------------------------------------------------------------------------------------------------------------------------- | |
| The blockchain explorer hosted at https://nuexplorer.ddns.net doesn't support the recent release of new currencies | |
| and the current code base is not very resilient. As a result of that the explorer is sometimes a couple of days behind | |
| and requires manual interventions beyond just restarting services. The new custodial grants are displayed incorrectly. | |
| This motion proposes to make some fixes without overhauling the base code to extent the lifespan of this explorer. | |
| @Cybnate will be the custodian of the funds which will only be released in full after the work has been delivered. | |
| The work will be completed by @2undroid at a cost of no more than 1,200 US-NBT. The custodial fee will be 50 US-NBT. | |
| An upfront payment of up to 33% of the estimated total may be agreed between @Cybnate and @2undroid. | |
| The following requirements will be met on delivery: | |
| - The explore status page will show information about the new currencies, in particular market price (in US$) and marketcap | |
| - Grants for the new currencies will be gracefully handled prohibiting the explorer to stop processing | |
| - Grants for EU-NBT, CH-NBT, X-NBT, JP-NBT and KR-NBT will be recognised as such on the 'votes' and 'votes/success' pages for grants. | |
| The work meeting the above requirements will be delivered within 8 weeks after this motion has passed. | |
| The NuShareholders pledge to transfer the funds to a custodial NBT address published by @Cybnate in the public forum | |
| within 3 days of the motion passing. | |
| ------------------------------------------------------------------------------------------------------------------------------- | |
| Please add the following in your client to support this motiont: | |
| <motion> | |
| This motion is deliberately not submitted as a custiodal grant. Unfortunately custodial grants triggers security measures halting trading | |
| on Bittrex at the moment. The Nu Team is still working to resolve this issue. Pending that a motion with a request to transfer | |
| funds from the liquidity reserves upon passing is requested. | |
| The discussion thread and more details when becoming available are here: | |
| https://discuss.nubits.com/t/draft-motion-to-update-nuexplorer-with-support-for-new-currencies/5835 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment