Out of curiosity, if we are using tor hidden service for masternode.. do we even really need a vps?
Could you just use another computer within a same network, because it will be using a .onion address vs. needing another ip address?
i think need is different onion address as it hash ip so different onion for each node Right, but what I mean is just have more computers (or xen virtualized instances) behind a same router.. because you're using Tor and not just a single IP / wan ip same router relate to same onion/ip unless multiple ip instance |
|
|
|
Out of curiosity, if we are using tor hidden service for masternode.. do we even really need a vps?
Could you just use another computer within a same network, because it will be using a .onion address vs. needing another ip address?
i think need is different onion address as it hash ip so different onion for each node |
|
|
|
got 10 masternodes now  will donate to dev soon after i have done setups thanks dev |
|
|
|
When this endi get most of coins |
|
|
|
Can you be more specific about the coin control fix? Was this simply a GUI change hiding the orphans, or is there something more fundamental that was fixed?
Not a GUI change, but under the hood there is something more fundamental. I changed the coin selection function to only return coins with at least 1 confirmation. Something about this with the new stuff in bitcoin core with HD wallets is causing the math to get thrown off, there is a "TODO" comment in the code from one of the core devs on one of the functions that says it has to be fixed  Anyway, the coin control issue and the orphans issue are two separate problems. The coin control bug is basically if you were breaking blocks down doing transactions really fast one after another, you could cause the wallet to get "out of sync", your balance would display wrong or maybe 2x your real balance, etc. and it is because of the math with the spent vs unspent coins and change addresses. dev prodigy thank him |
|
|
|
so what exactly am i looking at? Wallet fix is done, masternodes and fork on monday?
5,255,295 DASH divide 531,544 CRAVE x 9.886848502 very undervalue |
|
|
|
all sell will be ate |
|
|
|
so what exactly am i looking at? Wallet fix is done, masternodes and fork on monday?
I am about to activate a masternode on mainnet. :evilgrin:  |
|
|
|
 Also added kinetic scrolling to the overview page (so you can scroll with your finger on mobile like in other apps). Fix for coin control I have it not show unconfirmed coins. This seems to be the root of the issue that throws it off. Unfortunately what this means is if you are splitting down a large block of coins in one address, you have to wait for 1 block in between each send.  moon tonight what a delite thanks dev  development amazing |
|
|
|
indeed between the master nodes, markets, burning etc will all completely overshadow the 1 CRAVE per pos block over time which will keep inflation to a slow crawl lol if any at all. great concept  dev kept pos low because as price rises and features rarity price increase |
|
|
|
When you decide to run a masternode your craves become unspendable?
Most important thing is that there is room for only 52 markets or 1040 masternodes. So many ways to use crave but only 520k coins in circulation. You can imagine how it will affect the price.
will be less, you are forgetting that thousands of crave will be burned to create blur someone need work costs masternode = profitable? |
|
|
|
|
what is better to buy masternode or keep coin split between blur/masternode?
|
|
|
|
|
just saw on twitter silicon valley press release?
|
|
|
|
Testing the fixes and adrenaline nodes now. I put the keepass stuff in too but don't really have a way to test it so I'd say avoid that for now. Just have to test the automated masternode payments function from staking again....have to wait for it to stake dev keep up the good work dont let negative comment effect we all behind you |
|
|
|
if dev solve problem with pos 2.0 it can be higher value that all other pos coins using 2.0
what problem with pos 2.0? there is no problem with pos 2.0 don't create a problem when there is no problem... the orphans I'm working on trying to solve the annoying Coin Control bug once and for all, I've also experienced it and it is kind of unsettling, if you split lots of blocks at once or do it from the RPC console, the wallet seems to kind of get "out of sync" with itself and takes a bit to "catch up" and show the right balance info etc. So for now, avoid splitting lots of blocks at one time. The guys who are experienced "stakers" know this is kind of an important feature to have, so its a high priority fix to get in now. In which case it isn't really a PoS 2.0 problem.. i have no problem with coin you dont understand if he improves pos user code all other coins will use as he has debugged it |
|
|
|
if dev solve problem with pos 2.0 it can be higher value that all other pos coins using 2.0
what problem with pos 2.0? there is no problem with pos 2.0 don't create a problem when there is no problem... the orphans |
|
|
|
|
if dev solve problem with pos 2.0 it can be higher value that all other pos coins using 2.0
|
|
|
|
|
sell and buys nearly equal see you on the moon
|
|
|
|
I'm scared to buy back in now, The second that buy wall gets pulled its headed right back down below 45k. I think I'll wait this out. Not 100% on this dev yet either, lots of talk but no show YET!
this best market fun in months |
|
|
|
|
Show Posts
