steps... so empty. it never ends?
|
|
|
Looking forward to the progress! Keep it up guys, nice to see some movement.
pointless movement.. i cant see why waiste time. love the closed source!
|
|
|
What do you guys thinks? We are considering our first pre-sale of Earth Dollar tokens for Feburary 29, 2015 on Leap Year. The date has not been set yet. since we are analyzing the Ethereum code to see how to integrate some new features into it. We are testing the color coin protocol to create a special edition of GREEN EARTH DOLLAR TOKENS, which will be tradeable for Green Earth Dollars. The Green Earth Dollars in addition to regular assets attached, we will be attaching a full Carbon Credit to each Earth Dollar. These Green Earth Dollars will allow companies who are interested in mitigating climate change to use the Earth Dollar to do so. Also, we are about 20 people working on the Earth Dollar white paper and manifesto. It includes social activists, economists, programmers, visionaries...etc. It's about 75 pages long so far. It is almost finished. There will be a livestream interview of the Earth Dollar on Dec. 10, 2015, around 8:30 pm EST from Rotterdam at COM21 (Conference of Movements), an alternative event to COP21 (Conference of Parties -- Climate Change Negotiations in Paris). http://com21.orgCurrently, we are recruting more team members. If you are interested, let us know. Check your dates? LOL they should ban newbie accounts starting new threads. why not to ban all new announcements. whe got tons of trash already.
|
|
|
what is the situation of current testing? same chain, forked when? current rules still same as testing git? hard to test without source or any info.. the client, i dont need.
|
|
|
So my next question to the community is this. DarkSilk mining algo. I don't want opinions or suggestions. Just answer back with one of the below options. Thank you SHA256 is good but WAY too hard to launch without someone forking it immediately. I would argue that CPU or Scrypt is prob best outside of the more excotic x11, keccac etc. A custom CPU algo can be made dont under estimate the big group of potential sha miners. lot of useless hardwares left from btc..
|
|
|
combinedsplitstakethreshold/split values are only in the code? values can not be configured with conf file. but you can do it by custom wallet, change values to what ever you want. ?
when diff goes higher you may want to use bigger inputs..
Split threshold can be increased prior to launch cisa to counter any issues prior to them happening how about adding those values to conf file rules? sounds better when you can adjust it by your balance. like some other coins have it. of course that can be changed later, it is not important to have it "fine tuned" now. there are more important things before that..
|
|
|
coins is still drifting alone without devs?
|
|
|
combinedsplitstakethreshold/split values are only in the code? values can not be configured with conf file. but you can do it by custom wallet, change values to what ever you want. ?
when diff goes higher you may want to use bigger inputs..
|
|
|
when new git code up to testing? nodes,explorer, etc..
|
|
|
Just purchased 515,410 Silkcoin. I also have 230,000 in buy orders. Thinking of breaking a million Should I do it? No - sell your coins and jump on the next train -samsunk jump off, if you cant read the code and see what this is coming to.
|
|
|
testing... working branch compiled fine with windows
Yeah but I am still working on the code cisa so it isn't actually functioning atm because of the changes in CTransaction/CBlock/CBlockheader. i know. it still got chain downloaded upto 11618... Please refrain from using it as I am testing and need to clear the chain regularly. not playing or staking on main net. see the funny stakes Are you saying you see the funny stakes or are you asking if there are funny stakes? nothing serious, waiting updates.. (dash reward rules ghosting) reminds me how ugly game they played, add broken diff retargeting to this: if(nHeight >= 5465) { if((nHeight >= 17000 && dDiff > 75) || nHeight >= 24000) { // GPU/ASIC difficulty calc // 2222222/(((x+2600)/9)^2) nSubsidy = (2222222.0 / (pow((dDiff+2600.0)/9.0,2.0))); if (nSubsidy > 25) nSubsidy = 25; if (nSubsidy < 5) nSubsidy = 5; } else { // CPU mining calc nSubsidy = (11111.0 / (pow((dDiff+51.0)/6.0,2.0))); if (nSubsidy > 500) nSubsidy = 500; if (nSubsidy < 25) nSubsidy = 25; Sorry I am confused. Lost in translation a bit. The code from you previous post (quoted above) is for GetBlockValue. This is my code currently: int64_t GetBlockValue(int nBits, int nHeight, const CAmount& nFees) { double dDiff = (double)0x0000ffff / (double)(nBits & 0x00ffffff);
/* fixed bug caused diff to not be correctly calculated */ if(nHeight > 4500 || Params().NetworkID() == CChainParams::TESTNET) dDiff = ConvertBitsToDouble(nBits);
int64_t nSubsidy = 0; if(nHeight >= 5465) { if((nHeight >= 17000 && dDiff > 75) || nHeight >= 24000) { // GPU/ASIC difficulty calc // 2222222/(((x+2600)/9)^2) nSubsidy = (2222222.0 / (pow((dDiff+2600.0)/9.0,2.0))); if (nSubsidy > 25) nSubsidy = 25; if (nSubsidy < 5) nSubsidy = 5; } else { // CPU mining calc nSubsidy = (11111.0 / (pow((dDiff+51.0)/6.0,2.0))); if (nSubsidy > 500) nSubsidy = 500; if (nSubsidy < 25) nSubsidy = 25; } } else { nSubsidy = (1111.0 / (pow((dDiff+1.0),2.0))); if (nSubsidy > 500) nSubsidy = 500; if (nSubsidy < 1) nSubsidy = 1; }
// LogPrintf("height %u diff %4.2f reward %i \n", nHeight, dDiff, nSubsidy); nSubsidy *= COIN;
return nSubsidy + nFees; }
Are you suggesting to change it? I am confused by your post This is where the difference lies in case people are trying to work it out: nSubsidy = (2222222.0 / (pow((dDiff+2600.0)/9.0,2.0))); if (nSubsidy > 25) nSubsidy = 25; if (nSubsidy < 5) nSubsidy = 5; } else { // CPU mining calc nSubsidy = (11111.0 / (pow((dDiff+51.0)/6.0,2.0))); if (nSubsidy > 500) nSubsidy = 500; if (nSubsidy < 25) nSubsidy = 25; read the early posts of darkcoin and see why they had to do it like this. and add the double.. instamine was hidden this way. btw. current code gaved negative stake about -2600drk/ block.. so what, there is time to test and fix.
|
|
|
testing... working branch compiled fine with windows
Yeah but I am still working on the code cisa so it isn't actually functioning atm because of the changes in CTransaction/CBlock/CBlockheader. i know. it still got chain downloaded upto 11618... Please refrain from using it as I am testing and need to clear the chain regularly. not playing or staking on main net. see the funny stakes Are you saying you see the funny stakes or are you asking if there are funny stakes? nothing serious, waiting updates.. (dash reward rules ghosting) reminds me how ugly game they played, add broken diff retargeting to this: if(nHeight >= 5465) { if((nHeight >= 17000 && dDiff > 75) || nHeight >= 24000) { // GPU/ASIC difficulty calc // 2222222/(((x+2600)/9)^2) nSubsidy = (2222222.0 / (pow((dDiff+2600.0)/9.0,2.0))); if (nSubsidy > 25) nSubsidy = 25; if (nSubsidy < 5) nSubsidy = 5; } else { // CPU mining calc nSubsidy = (11111.0 / (pow((dDiff+51.0)/6.0,2.0))); if (nSubsidy > 500) nSubsidy = 500; if (nSubsidy < 25) nSubsidy = 25;
|
|
|
testing... working branch compiled fine with windows
Yeah but I am still working on the code cisa so it isn't actually functioning atm because of the changes in CTransaction/CBlock/CBlockheader. i know. it still got chain downloaded upto 11618... Please refrain from using it as I am testing and need to clear the chain regularly. not playing or staking on main net. see the funny stakes
|
|
|
testing... working branch compiled fine with windows
Yeah but I am still working on the code cisa so it isn't actually functioning atm because of the changes in CTransaction/CBlock/CBlockheader. i know. it still got chain downloaded upto 11618...
|
|
|
testing... working branch compiled fine with windows
|
|
|
would it be considered as bad action if i would release crave wallets that have masternode payment tweak added? those ibm guys could fix it in no time..??
What IBM guys lol? I don't see any IBM guys. they are runout
|
|
|
would it be considered as bad action if i would release crave wallets that have masternode payment tweak added? those ibm guys could fix it in no time..??
|
|
|
just tell when its ready to compile.. waiting In reality it's never ready to compile because I am none stop working on it. I will let you know when I have tested changes. There is still a way to go. yes, work you have done, and still todo.. will test as soon as the code can be compiled. and test nodes updated.
|
|
|
just tell when its ready to compile.. waiting
|
|
|
|