 Show Posts
|
|
Pages: « 1 [2] 3 4 »
|
ROBOCPU MINEABLE CRYPTOhttps://roboproject.org
Wallets | Source Code | Block Explorer
SPECIFICATION
Algorithm: Argon2d
Block Time: 2 Minutes
Difficulty Retarget: Every block (DarkGravityWave v3)
Max Coins: 105,000,000 ROBO
Mining Reward: 50 ROBO
Halving Interval: 1,050,000 blocks (~4 years)
have fun! |
|
|
|
On the developer's site it was indicated that the version v.0.15.X was a test version and all coins will not be accepted on version 1.0.0.0. When I started version 1.0.0.0 there were 0 coins, all the coins that were obtained earlier on the version of the wallet 0.15 (2500 ~) were marked as - generated but not accepted.
And v1 has another algoritm.
This is true. Both of these should be considered experimental and for testing purposes only. Relaunch of the v1.x variety is still pending. |
|
|
|
|
I've been doing a lot of reading and simple tests. I have decided the current block chain will be killed. Or at least no longer supported by me. If you're using v0.15.2 please stop mining, it was highjacked during an experiment. Download links from the website will also removed.
I am not giving up on ROBO, and my sincere apologies for any time wasted (even to the asic person). But in order for me to come up with a better PoW scheduling I need some time on a good "testnet" that can be wiped clean at any given time.
Some of the alternate algo's look good, and after experimenting with basic fixed time throttling + adding new data to blocks + network validation... It appears as if swapping the algo would actually be alot easier to do.
I appreciate everybody's patience with this.
|
|
|
|
Also is it possible to restart the whole block chain, after any changes are made, as this anti-social ASIC minor will be sitting on a large pre-mined pile of coins.
IMHO, yes, yes it is. see my post before this one. I'm going to need some time to figure out how to actually pull this off. You mentioned nodes checking timestamps of previous blocks. I agree that's a good place to start... the problem is blocks don't include data about the node that generated it. In a real world setting miner A and miner B could both generate a block within microseconds of each other... in that case the block should be accepted, but if from the same source node reject it, ban it. The way I see it extra data needs embedded into the block chain so that all peers can perform validations against the node which solved the block. Problem is, again, how to ensure a hacker doesn't randomize identifier information? Low level cryptography and network security aren't my expertise. It'll take a good amount of time for me to figure it out.. unless somebody else could point me in the right direction. |
|
|
|
"blocks": 14516, "currentblockweight": 4000, "currentblocktx": 0, "difficulty": 908106.801590743, "errors": "", "networkhashps": 5329237777407.467, "pooledtx": 0, "chain": "main" } owwwww soon diff 1million...and networkhashrate go beyond jupiter. not sure i will let my pc mining robo core  its sad, this token sound good. We're down, but not out. Heads up, probably going to reset the block chain and relaunch. I think it's early enough that it would be ok do so. What do you guys think? |
|
|
|
Can you look into the license terms of the original source code (MIT I guess), maybe you could include a closed source code in there.
Or somehow use multiple algos which switch depending on certain criteria.
Thats one i was thinking of too. I know that the source has to be open for most exchanges to accept coin, but can it not be closed initially? Also up for hash capping if possible...workout whata decent AMD/INTEL desktop pc hashes at, and allow no more than double...for example. BTC code = MIT, Qt = LGPL, both use other open source libraries covered under the same or different licenses. It's not that cut and dry unfortunately. I know that throttling would work, but somehow the network needs to validate it on a node/block basis (or something). Otherwise our ASIC pals will just do the same thing they did with RPC commands. If nodes, especially full nodes, can determine if a block was generated outside of the internal wallet code, then all it has to do is reject the block and ban the node which submitted the block. <---- another hypothetical idea. |
|
|
|
Unfortunately this project will have to open up in the traditional way for ASICs and others. That's ok, I'd rather see it live on than die.
Note to all, I'm going to adjust the PoW scheduling to react better with ASIC level hashing. It'll be more or less the same as it is now with less extreme difficulty adjustments. And... as with the 0.15.2, this next release will be a mandatory update. I'll keep the board well informed of the status.
No No NO! To ASICS... Please don't do that. That makes this coin no different from every other broken ASIC coin....please stick with the plan. If people don't want to stay, fine, let them go, but enough people will stay to mine coin. It only needs 2 people to actually keep coin alive, and from there it can grow steadily over time. Please try and limit back to cpu only via wallet only...if you do, your coin will stand alone against a tide of sh*t coins... Give it a chance...as they say Rome wasn't built in a day J I tend to agree. Is the fact that it's hard to mine really a bad thing? If the dev can somehow have it so it works via wallet mining etc only. I'm more than happy to put my time into mining this coin and having wallet open and could even host a node if needed if it's easy enough to set up a node for the wallet. total agrre no asic please but the initial idea was good but sha means asic so.... i will let my pc mining and will see.  { "blocks": 14031, "currentblockweight": 4900, "currentblocktx": 1, "difficulty": 231473.3310863087, "errors": "", "networkhashps": 365652529055.8644, "pooledtx": 1, "chain": "main" } can you lock only for wallet, pools are horrible for simples miners. but somebody has created a custom build which brings back RPC commands needed for ASIC mining. Whomever did this is destroying the future value of ROBO ... still thinking about how to overcome this. Swapping out the algorithm might be the only option, but it's going to take a good amount of time for me to learn crypto-programing. If any crypto devs are out there... I'm up for ideas on ASIC resistance. Think outside of the box! If we can figure this out, it'll be a game changer... ASIC person, I really wish you could see the massive potential here. High level ideas: - block-submission throttling (e.g. even if an asic infiltrates, the network would reject blocks when they come in to fast) - hash-rate throttling - geared toward the CPU miner. - adjust local hashrate one-by-one so all nodes on the network have an equal shot an solving a block. - devise validations on blocks that fail when they are submitted externally - even possible? I have no clue at this point. Don't know if any of that will come to light, just some thoughts I've had since yesterday. Request for input from other developers. |
|
|
|
Unfortunately this project will have to open up in the traditional way for ASICs and others. That's ok, I'd rather see it live on than die.
Note to all, I'm going to adjust the PoW scheduling to react better with ASIC level hashing. It'll be more or less the same as it is now with less extreme difficulty adjustments. And... as with the 0.15.2, this next release will be a mandatory update. I'll keep the board well informed of the status.
No No NO! To ASICS... Please don't do that. That makes this coin no different from every other broken ASIC coin....please stick with the plan. If people don't want to stay, fine, let them go, but enough people will stay to mine coin. It only needs 2 people to actually keep coin alive, and from there it can grow steadily over time. Please try and limit back to cpu only via wallet only...if you do, your coin will stand alone against a tide of sh*t coins... Give it a chance...as they say Rome wasn't built in a day J I tend to agree. Is the fact that it's hard to mine really a bad thing? Its not so much about the "hardness to mine", but more about the "fairness to mine". If the coin remains only cpu and wallet bound then potentially virtually anyone can mine it with a simple home pc and have a good chance of winning a block, although the hashrate might be quite high, each miner will have a similar hashrate, maybe half or double some one elses but that's about all. The second you can rpc, then you can either "solo pool " multiple pcs or worse start to use gpus, then the ratio to a guy using 1 Celeron 1 core vs 1 guy with 6 gpus becomes enormous, so all small miners are virtually killed... The problem them explodes the second ASICS can mine. Although at that stage pools help, by allowing the small guy a chance to submit some shares the earmings are too low. So i'm all for any coin that is locked to wallet mining. As for the current, massive hash day1, exchange day2, dump day3...I am mining several coins where they total nethash is around 2-10K, and there are only 20-50 miners worldwide, only on 1-2 exchanges and yet we are all making substantial money, so I like the slow burners that take a while to get established...for me mining is a cheap, long term hobby, and every so often you get lucky. (I made a huge amount of 1 random coin where in 3 hours I mined 5000 coins, at 2 sats, 4 months later they went to 22,000 sats...that to me is what mining is really about, randomness, fun and luck) I have no interest in sweating every MHz or .001% price change every second....just be a sloth, it works great  Btw, living in the UK with very exp electricity, I have never made a penny joining the ratrace, but the example I have given is just one my about 50 random coins that have given great rewards...but all pure luck, that's why I mine over 400 coins currently. You never know which might be a good one so give them all a chance. J The problem is that somebody went against the grain and re-enabled RPC commands getblocktemplate and submitblock in a custom build. They obviously don't see how popular this could be.... and that's a crying shame. The only way I know of to prevent that is to make this closed source... but that violates many open source licenses... not willing to do that. Could swap the algo, but even then ASICS will come in eventually... look at X11. My specialty is audio programing and DSP which I do for a living. So figuring out some crazy crypto algorithm isn't exactly my cup of tea... it'll take some major RND on my part to implement a new algorithm. So IDK, I'm going to keep thinking about where to go. I'm fully aware that opening up the RPC commands in the official build will kill interest of the project. But if I don't do it, then there's a small group of mega hashers sucking down all the rewards. At least re-enabling RPC will let others easily join the mega hashing party. ASIC guys: the more you mine with your custom setup... the more you are killing the future value of this project. - So either you're in it to see success, or your in it to be greedy... the latter isn't going to make you or any of us any real money with ROBO... so good luck with that. |
|
|
|
|
Unfortunately this project will have to open up in the traditional way for ASICs and others. That's ok, I'd rather see it live on than die.
Note to all, I'm going to adjust the PoW scheduling to react better with ASIC level hashing. It'll be more or less the same as it is now with less extreme difficulty adjustments. And... as with the 0.15.2, this next release will be a mandatory update. I'll keep the board well informed of the status.
|
|
|
|
It was a good try anyway. I just hope some of you guys out there with normal computers got some rewards. |
|
|
|
I see a couple of options.
1. Go for the gold. Let's open it up and compete with the other coins that use this algorithm. You seem to have heart and love the game so this could be an option especially if you have a bunch of us that will back the coin.
2. Implement a multi algo approach such as Digibyte.
I know this stuff is hard to do. In 2014-15 I started a coin that was a clone of Mintcoin called Cornerstonecoin. The community can be harsh and I gave up. However, what you have started could gain steam. I also know you are doing this for the fun of it and your love of the concept. If you really want it to succeed, it will. Personally, I would go with something similar to option 1. What have you got to lose at this point?
Option 1 would be alot easier. I think I'd want to tweak the PoW, or just completely revert it back. Otherwise, difficulty is gonna pulse like a saw tooth wave forever!!!! There is some cool stuff I want to do with just the UI and daemon interaction anyway. |
|
|
|
|
I'll have to think about where to go next. My brain hurts!
|
|
|
|
|
"{
"blocks": 13699,
"currentblockweight": 4000,
"currentblocktx": 0,
"difficulty": 8192,
"errors": "",
"networkhashps": 114692712835.9859,
"pooledtx": 0,
"chain": "main"
}"
looks like they got us. pretty easy to bring back the RPC commands and do a custom (compatible) build.
So now there's a decision that needs to be made... revert the PoW code to the original? Or just let it run and see how the behavior plays out over the course of time?
|
|
|
|
i start mining but difficulty is very high for a new coin. where can i see my hashrate on the debug mode in the wallet? it say the network hashrate but i not see mine?
"blocks": 13363,
"currentblockweight": 4000,
"currentblocktx": 0,
"difficulty": 8,
"errors": "",
"networkhashps": 157004684.978029,
"pooledtx": 0,
"chain": "main"
}
Difficulty 8 is alot better than 100, which is where we were yesterday. There isn't a way to see local hashrate currently. I'll have to revive that particular code from bitcoin's source. yeah sure 8 is better than 100 diff, but for a new coin 8 diff is HUGE, mostly when i mine news coins they have less than 0.0xx diff. some blocks i founded were refused, any idea? "some blocks i founded were refused, any idea? " because when the difficulty resets to a minimum, then everybody mines lightning fast. just double click the transaction in the GUI and read the last paragraph. "... If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours ..." |
|
|
|
i start mining but difficulty is very high for a new coin. where can i see my hashrate on the debug mode in the wallet? it say the network hashrate but i not see mine?
"blocks": 13363,
"currentblockweight": 4000,
"currentblocktx": 0,
"difficulty": 8,
"errors": "",
"networkhashps": 157004684.978029,
"pooledtx": 0,
"chain": "main"
}
Difficulty 8 is alot better than 100, which is where we were yesterday. There isn't a way to see local hashrate currently. I'll have to revive that particular code from bitcoin's source. yeah sure 8 is better than 100 diff, but for a new coin 8 diff is HUGE, mostly when i mine news coins they have less than 0.0xx diff. some blocks i founded were refused, any idea? "but for a new coin 8 diff is HUGE" - maybe ROBO is gaining traction faster than most sh** coins. We're on the verge of being the first truly CPU minable crypto currency. I rewrote how PoW difficulty is scheduled and we're experiencing the result of that after days worth of 1hr plus block times... it's gonna be a day or two to see how this solution really will work. It seems to be leveling toward an 8 difficulty... we'll just have to wait and see. |
|
|
|
i start mining but difficulty is very high for a new coin. where can i see my hashrate on the debug mode in the wallet? it say the network hashrate but i not see mine?
"blocks": 13363,
"currentblockweight": 4000,
"currentblocktx": 0,
"difficulty": 8,
"errors": "",
"networkhashps": 157004684.978029,
"pooledtx": 0,
"chain": "main"
}
Difficulty 8 is alot better than 100, which is where we were yesterday. There isn't a way to see local hashrate currently. I'll have to revive that particular code from bitcoin's source. |
|
|
|
i start mining but difficulty is very high for a new coin. where can i see my hashrate on the debug mode in the wallet? it say the network hashrate but i not see mine?
"blocks": 13363,
"currentblockweight": 4000,
"currentblocktx": 0,
"difficulty": 8,
"errors": "",
"networkhashps": 157004684.978029,
"pooledtx": 0,
"chain": "main"
}
Difficulty 8 is alot better 100, which is where we were yesterday. There isn't a way to see local hashrate currently. I'll have to revive that particular code from bitcoin's source. |
|
|
|
|
Good afternoon everybody! New PoW strategy should kick in at block #11886. I suggest you ban any nodes still on version 0.15.1
|
|
|
|
how can i see if i found a block?
canīt see my hash power, i just follow the steps, and all morning mining i guess, my balance is 0!!!
If you find a block, 50.0 ROBO pops in your balance. Difficulty right now is 100.0, which is pretty tough to mine for most computers... hence the PoW restructuring, which will kick in later today. I still need to write some bits that compute the local miners hashrate... I'll make sure to do that by the next release. For now, open the task manager (or equivalent) and look at the CPU performance. If your CPUs are maxed then you are mining. |
|
|
|
How to open the wallet and start mining automatically?
There isn't a feature that automatically starts mining when the wallet is opened. Here's the mining guide thoughI could possibly add this functionality to the wallet GUI in the future. |
|
|
|
|
