Yes, I saw that doc, smart guy, head hunted by a large company so they can skim the top off the world's stocks, alls fair in love and Wall street I suppose, but the difference was they were not tied down to the mathermatical rules of a blockchain consensus (or any other law for that matter!)Sub-Ether, This is fantastic. You would be perfectly qualified for a project I have in mind. Kind of related to this documentary Ghostplayer posted here:
Algorithmic Forex Trading! ...
The project would involve only one customer so it shouldn't need too much for database structure. The main code would work with masternodes and how they interact with each other. Specifically, high frequency manipulating of masternode inputs for hijacking payments to a specific address.
LOL!
)
Attach a large Dash logo sticker on the side of car (like Uber do) and we'll know who you areGood to hear you are visiting the Netherlands, planning also to join the meeting as it is nearby
if you would need any local assistance we are here to help out ( including being a taxi if needed
Thanks ! , might actually do thatAttach a large Dash logo sticker on the side of car (like Uber do) and we'll know who you are
, Instant taXi Free of Charge ( for DASH members only )
Are you saying the devs shouldn't eat or pay their bills? I think it's been a long time coming for them, how long do we want to make them wait? A C++ programmer can make a whole lot more money somewhere else right now, why should we make them work for free?May be I got an idea for the "Core Development team budget" to have something more "long term", but maybe it will take too much time to become effective:
The idea is to make something that will (in future) even don't need to take money from the budget system, but it will take time to become interesting.
Instead of paying directly the Dev Team from the budget, regroup those DASH to make MasterNode and the revenue of those MN will pay the core dev team.
The proposal for this month is 3,000$, this could be 3 MN. But dev will receive nothing this month. So next month they could receive payment from those 3 MN and create 3 more. At beginning this will be few but with time maybe the revenue of all MN created will be enough to sustain a good "Dev Core Team" without need to cut the budget, and so budget can be use for other things.
Maybe we can split those 3,000$, half to pay "dev core team", half keep for the dev core payin's MN.
I know that maybe the beginning could be hard and low paying, but if we look at future and long term I saw only benefice :
-No more cutting from budget to pay a keep "Dev core Team" motivated.
-More MN for the network.
-More DASH hold in MN.
Though?
EDIT: with a quick calcul (DASH=3$ and MN earning per day = 0.5) we'll need ~66 MN to have a 3000$ monthly revenue
Edit 2: Hmmm something also we must think about : who are the proprietary of those DASH? and those DASH will be hold in MN for the eternity? lol
If we add masternodes to the network, existing masternode owners lose a piece of the earnings (about 1/3000) less. Not opposed to the idea, but it sure sounds better to an outsider if the blockchain is paying rewards that are used for development vs "interest" on a set of nodes.May be I got an idea for the "Core Development team budget" to have something more "long term", but maybe it will take too much time to become effective:
The idea is to make something that will (in future) even don't need to take money from the budget system, but it will take time to become interesting.
Instead of paying directly the Dev Team from the budget, regroup those DASH to make MasterNode and the revenue of those MN will pay the core dev team.
The proposal for this month is 3,000$, this could be 3 MN. But dev will receive nothing this month. So next month they could receive payment from those 3 MN and create 3 more. At beginning this will be few but with time maybe the revenue of all MN created will be enough to sustain a good "Dev Core Team" without need to cut the budget, and so budget can be use for other things.
Maybe we can split those 3,000$, half to pay "dev core team", half keep for the dev core payin's MN.
I know that maybe the beginning could be hard and low paying, but if we look at future and long term I saw only benefice :
-No more cutting from budget to pay a keep "Dev core Team" motivated.
-More MN for the network.
-More DASH hold in MN.
Though?
EDIT: with a quick calcul (DASH=3$ and MN earning per day = 0.5) we'll need ~66 MN to have a 3000$ monthly revenue
LOL...
Just trying to be funny. The Dash system should be secure enough that hijacking can't happen.
Moli, at $2 per day at current market value per masternode income split between 4 developers, we will be fighting off c++ programmers queuing round the block for a job
LOL..Moli, at $2 per day at current market value per masternode income split between 4 developers, we will be fighting off c++ programmers queuing round the block for a job
Indeed-simulink was mighty powerful I always meant to go back to it but never found a decent application. I like to visualize the markets as positive and negative feedback loops like in electronics, the masternodes themselves provide price dampening in both directions due to market demand (as you suggest)
.
The design in my head is nearly unlimited.
and for voting with a single masternode change "vote-many" to "vote"
end-result should be : "Voted successfully"
To check the current votes : ./dash-cli mnbudget show
Currently 187 YEAS for all three budget proposals
If you want to specifically vote against a specific budget because you dont agree with it then change the "yes" into a "no"
./dash-cli mnbudget vote-alias mn1 eac63...87 yes
(where mn1 = the alias of one of the masternodes)i'm having a deju-vu feeling right now
)