Topic: |ANN| CrocodileCash | PoW/DPOS/PoS Hybrid | Snap Them Up Fast | Android Wallet | - page 15. (Read 61412 times)

And? It will split your balance to a bunch of small piles, so you cannot split it only 3 times
Above is explained why.

BTW I disabled staking on a node at 8:00



Coincidence? Don't think so))

the general rule (with this form of POS) is that your input weight increases probability (other forms do not use coin weight).
bigger input = more probability
older input = more probability

each input is hashed every second to see if it can stake. if the outcome is lower than the diff you win !!
unless it orphans

the other factor is that min stake age ( 2hours ) effects overall probability because it is time that you cannot stake.

if probability holds correctly.
1 input that takes ~ 24 hours to stake, will pay 22 hours of interest (total stake time - min stake age).
split up
4 inputs will take 4*22 plus the 2hours min stake or ~90 hours, and pay 88 hours of interest

1 input time ratio for staking will then be 22/24
vs
4 inputs time ratio will be 88/90

4 inputs gives you a better probabilistic time ratio for staking. and probabilistically you will not miss out by splitting.

however with 2 hrs min stake age, the difference is not as pronounced as a 7day min stake age.
also this does not take into accountt compounding returns
also
many small stakes raises difficulty.

..

if you're really keen, you can adjust settings when you compile daemon
https://github.com/RangaBoom/CrocodileCash/blob/master/src/wallet.cpp#L18
unsigned int nStakeSplitAge = 1 * 24 * 60 * 60;
int64_t nStakeCombineThreshold = 1000 * COIN;

the basics is that if your input is under 1 day old it will split,
if it is over it will recombine unless it's over 1000

this is also a good way to recombine all yr piddly inputs if you want,

example - combine into single input
unsigned int nStakeSplitAge = 1 ;
int64_t nStakeCombineThreshold = 100000000 * COIN;

split into millions of teeny ones
unsigned int nStakeSplitAge = 9999 * 24 * 60 * 60;
int64_t nStakeCombineThreshold = 1 * COIN;

..

on another note,
glad to see croc going full steam, i dont follow threads and just randomly checked in today to see much discussions !!

i'm available for advice or help if you pm me
and will happily help with osx wallets as required.

You have to actually specify how much you want to stake.

There is an option...I think it is reservebalance, that reserves a portion of your balance to stake.

Yeah I hope I was wrong. But despite of that, the community keeps on growing and are collaborating for the good of the project. Goodluck to us.

How? It splits inputs.

I think lightning network is kind of ironic for our chain. On the other hand, if again it's fairly simple to merge Bitcoin's implementation...no problem.

I do not think this should be our priority though. Using CrocodileCash should be our priority.

If you go forward  with Segwit integration will the next step be lightning network (when its finish)
what do you think ?
the code updates could be part of your Developer road map, apart of Croc-lo & the other things you mention some pages ago you wana do

When I was looking at PoS code it seems to be nearly random. I think it is myth that "more balance = lower difficulty". What actually happens is there is a probability of a block to be a stake block. You can stake multiple times (lets say, 1000 CROC, staked 10 times = 10,000 CROC staked) to find staked blocks faster. Or you can stake the whole 10,000 CROC once. The payout will be greater, but the chances of finding a stake block will be lower.

My setup is, I'm staking about 10,000 CROC split up 3 times. I make much more this way.

I will checkout the CPU usage issue and make it my priority number 1.

Edit: re-compiling CrocodileCash with -pg to do the profiling with gprof. I'll keep you updated.

Segwit integration should be straight forward...Just have to pull changes from Bitcoin core. Note: I have no idea how this will break the current network

2-4 though I don't care for. I do NOT want advertisements in a wallet. It's a security concern.

Intelligent contracts - yeah maybe if this was an Ethereum fork. But it aint!

well....  If so. it's easy to implement.... Will be added soon...

Isn't it too early to consider despair? Seems like the dev didn't post too often in September anyway, though this absence of posts is the longest.

you pull that info from CMC or worldcoinindex API
https://www.worldcoinindex.com/apiservice

totaal wallet value could be something like : balance x "Price_usd"=

Something like this

https://ibb.co/jKreQb

its okay im just ask

Do you know how exactly works PoS? I was reading that staking has difficulity that depends on summary wallet balance (more balance - lower dif),  but how it guess the task? Using CPU?  But XLR and WYV wallets currently consume 0% and they are at staking too. Only CROC wallet consumes CPU at my server

I even don't know how it works - calculates estimated btc value just using highest bid? or checks all bids and their amounts?   It should be a heavy process for the server

Proposal Developers

1) activation of segwit.
2) Implementation of advertisements in the wallet to generate revenue.
3) use of the CROC blockchain in the field of transport and logistics.
4) Intelligent contracts: rent of a small percentage of the power of your computer to make calculations in different fields (research, company, laboratory, etc.).

can you put estimated value in balance wallet (just like bittrex wallet balance).. maybe total in btc, usd , or ruby ..
for me its easy to see total estimated value in wallet balance   

what do you think?? can over 1k sats each? 

Well I will think about 

Great work banding together in this time of need, don't let distractions get in the way