Any particular reason the Dash.org Domain Name budget proposal is showing up in red on dashvotetracker ? http://dashvotetracker.com/ Edit : shouldn't the payment number be 4/4 for next superblock ? As the proposal itself ends 21st of april 2016 ? I think it missed the first payment. The correct information to show would be 3/4 because it was only payed 3 times as you can see in the explorer. https://chainz.cryptoid.info/dash/address.dws?Xr122HobAmPTQV5qe9jHuwxVVFFCd6P4E3.htmOn the other side dash-cli is reporting all 4 payments were done because the code does not check if the payment was done. It only counts blocks. {"Abstains":0,"BlockEnd":456940,"BlockStart":382168,"FeeHash":"f3233c0c55adbbcabff5c51d841c8c784e15e336882c3acce538bcb921bf9198","Hash":"54e800e5c462a9bbc905ef523058ec76fe6207bcbd547a4cc9d38587eb954728","IsEstablished":true,"IsValid":true,"IsValidReason":"","MonthlyPayment":2100.0,"Name":"dash-org","Nays":145,"PaymentAddress":"Xr122HobAmPTQV5qe9jHuwxVVFFCd6P4E3","Ratio":0.92152704, "RemainingPaymentCount":0,"TotalPayment":8400.0,"TotalPaymentCount":4,"URL":" www.dashwhale.org/p/dash-org","Yeas":1648,"fValid":true,"fixed_URL":" https://www.dashwhale.org/p/dash-org","timestamp":1457376751735} |
|
|
|
"USD valuations would also be created via quorum and an average price over a period of 7 days would be used to stop people from attacking the implementation. (e.g. if you dump 10000 coins right before the budget is finalized, you could drop the price by 10% and get 10% more coins as a result, right? To stop this we’ll use quorum based averages)."
Evan,
Can you please explain a little more how this will work?
thanks
Any details on this? |
|
|
|
|
"USD valuations would also be created via quorum and an average price over a period of 7 days would be used to stop people from attacking the implementation. (e.g. if you dump 10000 coins right before the budget is finalized, you could drop the price by 10% and get 10% more coins as a result, right? To stop this we’ll use quorum based averages)."
Evan,
Can you please explain a little more how this will work?
thanks
|
|
|
|
|
yep, you're right! Not a native english speaker so please excuse me my underdog english.
glad you understood my point anyway
|
|
|
|
|
Evan,
I would like to invite you to have dinner at my house, so we can chat about bitcoin (and maybe dash).
I believe this is of great value for you, so the ticket, with dinner included and after drinks, is $5000.
I suggest you create a proposal and submit it. Pretty sure it will pass.
Edit: you can bring Otoh if that helps...
|
|
|
|
From the creators of the Dash N Drink, we bring you a phase 2 proposal called Vendor-Experience. After all of the interest the Dash N Drink showed in Miami, we anticipate future products we create and present will do the same. Please vote and or ask any questions. https://www.dashwhale.org/p/Vendor-ExperienceWe believe the best way to grow Dash is to give users a place to spend their Dash. Dash has an advantage over any other crypto with InstantX that can enable point of sale purchases without risk. We plan to utilize this advantage to show projects in the real world. The initial project we implemented was the Dash N Drink soda machine. The key to making this project was to implement InstantX detection and trigger a machine credit. This has now opened the door for the next phase. The next projects we will work on will include more sophisticated interfaces that will take engineering and software to connect to properly. We will be updating mobile wallets so they work quickly and easily. We expect to deploy actual products in actual stores. The core team members coordinating this project are Camosoul, Moocowmoo, and Solarminer. dash-cli mnbudget vote-many 1cfc2525f33d8dee81640f6860fc85751acea552724ec58d6619f7fcee694ea1 yes Solar, the dashNdrink was epic, really good idea, and yes I agree to vote for budget to made more products like this (using advantage of instantX). But why put a proposal with an end paying period in 2024? Why so long? This is really too long, I don't think the MN owner will vote for something so long... why not make a 3 months proposal? And after the 3 months made another? while a pain - They can be down voted in any month not to pay out Hello! It’s definitely interesting to see how people are using the budget system already although only a few months old. The soda machine was a great project to show off one of the main features of Dash, instant transactions. Now I’m really interested to see where you’re going with this project. Can we have some more information about the project, the vending machine and how you’re planning on operating this? Here’s some of our main concerns: We don’t know what’s happening to the vending machine that was already made, who owns this vending machine and what’s the plan for it? What are you going to be purchasing with the $3000? Can you give us an itemized breakdown? Can you give us a plan on how you aim to use these funds each month? Would it be possible to come up with milestones for this project? What are you planning on accomplishing? How will it benefit the ecosystem? Are you planning on selling vending machines, components of them eventually, or something like this? Who will earn these rewards? I would assume if the masternode network is funding your operation, it should receive a cut of the profits each quarter paid out as dividends. I would like to also establish some sort of agreement between yourselves and the Darkcoin foundation as well to make that agreement official. I’m curious what the answers are, as that will inform the decision of the masternode network. Funding is starting to get tight on the network so we definitely need to be careful that we’ll have great return on the network’s investment. Regards, Evan (xposted on DashWhale) We view this proposal as a core requirement for Dash adoption, not something that is for a single merchant application or single product. If anyone would rather only support this proposal for 1 month/3 months just vote it out when you want. We plan to deliver and keep pushing the envelope of possibilities. We plan to initially target easier devices and as we learn get to more complicated infrastructure projects. This is the plan as we have it now, but that could change based on vendor participation or types of products available. Vending machine with multiple products that uses a custom interface.- Design software to communicate with interface, implement multiple product selection within the dash wallet. Gas pumps- Design software to communicate with the pump controller, implement a wifi captive portal checkout with one product. Dash Sky Store Checkout- Design a wifi captive portal with multiple products. Implement the Dash Fast Lane - no register checkout. We will be getting assistance from inside and outside the Dash space. Each application will win press releases and additional status as a leading crypto similar to how we won publicity with the Dash N Drink. As for the questions about what happens to the products after we are done, we expect them to be in the hands of a merchant who will actually use them. This will bring ongoing publicity along with proof of concept for other merchants to adopt and a base for testing. The valuable part of all these projects is the software, publicity and to gain adoption. The software will be open source as much as possible. The intent is not to make a business to sell products but to show how products can be used in real world scenarios. Just seems a bit rushed - not enough details $3000 a month and $36000 per year really does need a HUGE explaination if it was a proposal from Evan you would all give a free pass without a blink core-team budget: 1176 DASH x 100 payments and normally he just spits out a TODO list (more kind of wish list) this proposal is as much important as core development. it should be core development. |
|
|
|
Hi all. Can anyone tell me how many Master Nodes Dash has at present? Thank you
You can track MNs using: 1. this graph http://178.254.18.153/~pub/masternode_count.png2. https://chainz.cryptoid.info/dash/ or https://chainz.cryptoid.info/dash/masternodes.dws to get more info 3. https://dashninja.pl/masternodes.html#mnlistdetail or http://www.dashnodes.com/index/masternodes/ to get even more detailed info 4. or simply via Dash Core wallet itself (Tools -> Information -> Number of Masternodes) ...
Has anyone run any numbers?
Is there a plan to phase out masternodes or reduce the amount needed to run a MN?
The number of MNs is designed to balance itself: the more MNs there are the less reward for every single MN. To reduce the amount needed to run a MN (i.e. increase the number of MNs) we would have to do a hard fork and ask everyone to split their MNs which would be a stress for the network. I think we are pretty fine with the number of MNs we have right now and there is no need for such action. If you are looking to run a MN but you do not have 1000 DASH you can join other people to run a so called shared masternode. There are some community members who offer such service (but be aware that you have to trust them your DASHs to run a MN for you). You always forget about dash-stats.com |
|
|
|
Prototype Update: Thanks to @salmion for our new design   Looking great, but what does oaeu mean? My keyboard is dvorak   I would prefer it as a chrome application rather than a chrome extension, because it emulates quite perfectly a standalone application. It's getting pretty! |
|
|
|
Just to make sure we are all on the same page, this is how the system currently works:
From dashninja:
A budget proposal is valid if the fee was payed and it was submitted to peers successfully.
A budget proposal is established when it is older than 1 day.
A budget proposal is alloted (will get paid on next super-block and is in the budgets projection list) when Yea votes minus Nay votes is more than 10% of total masternodes.
The system is designed to resolve controversy, the way it works the yeas in the proposal have to win the nays by at least 10% of the network. If there is a polemic proposal where 10% of the network says No then you need at least 20% of the network to say yes for it to get approved for a total 30% participation. It self adjusts and I don't think this is well understood. Hope this helps.
Also, we don't have enough time to review proposals. Generally, people are just giving us a couple of weeks, that's not enough to discuss and argue. I think, for this to work best, we should do this in 2 steps. First, gather the proposals, then spend 1 month discussing them before they're open for voting. Then vote. There's no need to rush any vote if the budget proposal is planned correctly. The only time constraints on a proposal's voting window are defined by the submitter. It's perfectly valid to submit a proposal that starts getting paid at a later cycle(s). In fact, I'd encourage future submitters to do just that, *especially* if it is a one-time payment. Here are next years cycle start blocks and approximate dates. Set your payment-start block's accordingly. block date
382168 - Sat Jan 16 01:20:00 UTC 2016
398784 - Sat Feb 13 21:40:00 UTC 2016
415400 - Sun Mar 13 18:00:00 UTC 2016
432016 - Mon Apr 11 14:20:00 UTC 2016
448632 - Tue May 10 10:40:00 UTC 2016
465248 - Wed Jun 8 07:00:00 UTC 2016
481864 - Thu Jul 7 03:20:00 UTC 2016
498480 - Thu Aug 4 23:40:00 UTC 2016
515096 - Fri Sep 2 20:00:00 UTC 2016
531712 - Sat Oct 1 16:20:00 UTC 2016
548328 - Sun Oct 30 12:40:00 UTC 2016
564944 - Mon Nov 28 09:00:00 UTC 2016
581560 - Tue Dec 27 05:20:00 UTC 2016
here's the script and math # 16616 / 576 = 28.8472 * 24 = 692.33
D0=$(TZ=UTC date --date="$(date --date="2015-12-07T08:27:12+0000")");
for block in `seq 382168 16616 $((382168 + (16616*24)))`;
do DD=$(TZ=UTC date --date="$(date --date="$D0") +692 hours +20 minutes");
D0=$DD;
echo "$block - $DD";
done
Also, I'd like to remind everybody of some important differences from typical elections that Dash's voting system has: (taken from masternode-budget.cpp) - Votes are counted every 16616 blocks - Votes can be recast at any time - Budget proposals remain on the network until: either 340 more nay votes than yay votes are cast (10% of total masternodes) or the proposal end block is reached - Approved budgets are paid in order of yay - nay votes - Approved budgets can be nullified at any time by recasting votes
Also, A bit of rumor control about "Evan controlling the budget system": Evan doesn't have enough masternodes online to pass anything. Neither do I. Even working together we couldn't vote the required 10%. From what I've gathered analyzing vote timestamps only otoh has enough masternodes provisioned to cast enough votes to pass a budget item. But even with approximately 600 masternodes (maybe less today), it would only take 261 no votes to prevent the budget item from passing. Additionally, the budget allocation is disbursed in order of yay - nay votes. So, even if somebody did sneak a budget item in at the last second, it would only be processed after all other approved budgets had been funded. -- I hope this post helps to dispel any concern about dash being controlled by whales. The way the system is set up, what is good for the currency will trump any few individuals' will to power. This is valuable info and it's gonna get buried deep in this forum. I would suggest someone includes this info in the official documentation. The budget system wiki is very, very incomplete. |
|
|
|
3000 BTC Huobi wall....Munched.
$1.4 Million dollars worth of bitcoin bought in around 90 seconds.
hard to believe it's a real transaction |
|
|
|
|
I think it's better to remove those bad links from your quotes
|
|
|
|
|
Show Posts
