Thanks to bitspill and others in our irc.freenode.net #axiomcrypto chat, we have a NOMP server up: http://176.9.59.110:9595/And thanks to all working hard on the CPU miner. Moving to C++ > C is not easy in this instance  |
|
|
|
when's on Exchange Dev?
We have reached out and are trying for fast listing! |
|
|
|
We welcome the discussion, this is why the thread is unmoderated. Some miners had trouble connecting, as the demand outgrew our server loads, with 200-400 clients connecting at once in the first 20 minutes. We added 4 large servers and changed maxconnections from 64 to 2048. It is normal for some miners to have orphans during a launch. We were offering tips to reconnect and correct any issues, all through launch. Thank you all for participating. Join in freenode IRC #axiomcrypto !!! New members of the community are working on building a p2p pool now.
https://kiwiirc.com/client |
|
|
|
sleep well while the botnet are working We have over 400 connections to the nodes, many miners are participating. Come join us, brother! |
|
|
|
|
We've fixed the nethash bug.
Theres a check at the beginning of the function in rpcblockchain.cpp, if the blockheight is greater than lastpowblock a nethash is returned, except lastpowblock doesn't exist so it is always true and always returned 0.
There are about 439 cores on the network:
1M * .00263999 / 6
6 being average hashes per second that we saw in our testings.
We will push the fix soon, non mandatory update. If you want to see your personal hashrate, open your debug.log. Showing it in the console will slow the miner down too much currently.
|
|
|
|
okay..thats enought..more than an hour on the right chain and found no blocks...so...this is the coin that botnet take overall..good luck guys and BYE!
Hi Doremi, Sorry to hear your frustrations. It's a bit different from the pool mining that many are used to. It depends on your CPU, how many cores, and it's raw mathematical processing power. Also, keep in mind that unlike pool mining where single blocks are divided up amongst all those mining, Solo mining if you hit the block you get the entire block which currently is 500 coins undivided deposited right in to your account for the upcoming stake phase. I would love to hear that you were mining and grabbed some blocks while at it. |
|
|
|
can anybody help me?
I've installed the wallet and I press "engage miner" but it appears as if nothing happens, how can I check if I am mining? Sorry for being such a terrible noob, I normally don't mine but thought this could be my first.
You can either: Press win + R notepad %APPDATA%\axiom\debug.log Hashrate info is there. Also you can right click your taskbar, choose task manager, see cores used. If you want to use more you can go to Help > Debug > Console type: setgenerate true # # = # of cores. Block explorer: http://e.axiomcoin.xyz/ |
|
|
|
|
Thank you for mining on your CPU! These are some of the many factors we took in to consideration when developing this algorithm and distribution model. Hash has become centralized and changed market conditions negatively. AXIOM is a game changer, we're looking forward to show you what we're capable of on a project that has a chance to succeed.
|
|
|
|
Why doesn't my hashrate and network hashrate show when I do a 'getmininginfo'? I don't know if it's worth bothering to mine right now. Mining anyway......
It's not showing up on getmininginfo because the normal hash rate is so low, compared to other algos We need to multiply by a million or so, then the number will be large enough to print. Thanks for helping to find the bug. We will build the fix soon, within 24 hours we see. For now you can see your personal hashrate statistics in your %APPDATA%\axiom\debug.log file. If any other coder would like to submit a patch to https://bitbucket.org/AxiomCryptocurrency/axiomwe will be happy! |
|
|
|
This smells like that broken Octane coin.
Why doesn't my hashrate and network hashrate show when I do a 'getmininginfo'? I don't know if it's worth bothering to mine right now. Mining anyway......
We are a new fork from PP > Nova > Black > Axiom! What a schlep to setup but anyways - done. Dev you are missing some folders in the source code. You must create an empty secp256k1 folder in /obj and then within that an empty /src folder. Unless I did something wrong.
Yes we will add it  Anyone think this is going to fry my CPU if I crank it to full speed? Right now I am running two cores and the inactive cores are at 63 C and the active cores are at 71C. I have a intel chip. I5-3450. (Yeah, I know it's old and crappy.) Desktop computer. I'd never solo mine on a laptop...
You can set number of cores to use by opening the wallet fresh and goto: Help Debug Window Console type in: setgenerate true # where # = the number of the cores. Now the default is conservative to prevent damage. Please follow on Twitter: https://twitter.com/AxiomCrypto/status/625194748291125248 |
|
|
|
premine = 379 blocks ??!!
We had 80 connections to wallet from launch time, many miners. Here is a graph of the CPU use just from connecting peers:  Come mine! |
|
|
|
A lot of forks are happening.  Diff is rising and we are adding two more strong nodes now. The nodes are in the DNS seeding and you can manually add: addnode=104.236.231.72 addnode=45.55.172.95 addnode=174.127.110.41 We will add 2 more servers quickly! If you have any problem compiling, make install: https://github.com/bitcoin/secp256k1i still fork with this nodes OFFICIAL CHECKPOINTING NODES are on block 341. If you aren't at this blockheight, close the wallet, open again, wait to resync. Our nodes are flooded with too many connections! New addnodes are coming!! A 32bit wallet dev ? The algo is very inefficient in 32 bit mode but we have included the code to compile in axiom-qt.pro if you like: DEFINES += USE_NUM_NONE USE_FIELD_INV_BUILTIN USE_SCALAR_INV_BUILTIN # 64-bit #DEFINES += USE_FIELD_5X52 USE_SCALAR_4X64 # 32-bit DEFINES += USE_FIELD_10X26 USE_SCALAR_8X32 Nevermind if I have to compile it as I dont know anything about compiling a wallet . I'll just move away from it in that case . We will compile one for you, please have some patience, and upgrade to a 64 bit OS soon Here is the compiled 32 bit windows wallet: https://mega.co.nz/#!FUUUjRqR!Kt0ic_atLG3DrcejKjqHqWpDscttWrUCmqYa5BEQf8QAnd WOW 400+ incoming wallet connections to the nodes! |
|
|
|
A lot of forks are happening. Diff is rising and we are adding two more strong nodes now. The nodes are in the DNS seeding and you can manually add: addnode=104.236.231.72 addnode=45.55.172.95 addnode=174.127.110.41 We will add 2 more servers quickly! If you have any problem compiling, make install: https://github.com/bitcoin/secp256k1i still fork with this nodes OFFICIAL CHECKPOINTING NODES are on block 341. If you aren't at this blockheight, close the wallet, open again, wait to resync. Our nodes are flooded with too many connections! New addnodes are coming!! A 32bit wallet dev ? The algo is very inefficient in 32 bit mode but we have included the code to compile in axiom-qt.pro if you like: DEFINES += USE_NUM_NONE USE_FIELD_INV_BUILTIN USE_SCALAR_INV_BUILTIN # 64-bit #DEFINES += USE_FIELD_5X52 USE_SCALAR_4X64 # 32-bit DEFINES += USE_FIELD_10X26 USE_SCALAR_8X32 Nevermind if I have to compile it as I dont know anything about compiling a wallet . I'll just move away from it in that case . We will compile one for you, please have some patience, and upgrade to a 64 bit OS soon Confirm Block 392NEW NODE:
addnode=162.222.181.215addnode=104.236.231.72 addnode=45.55.172.95 addnode=174.127.110.41 MORE NODES COMING anyone not at block 392, close wallet, reopen, wait to ask node fresh - we have many hundreds of connections to manage here!
BLOCK EXPLORER LIVE
http://e.axiomcoin.xyz/
We have years of POW, come mine and stake!! Min stake age is 4 hours. |
|
|
|
A lot of forks are happening. Diff is rising and we are adding two more strong nodes now. The nodes are in the DNS seeding and you can manually add: addnode=104.236.231.72 addnode=45.55.172.95 addnode=174.127.110.41 We will add 2 more servers quickly! If you have any problem compiling, make install: https://github.com/bitcoin/secp256k1i still fork with this nodes OFFICIAL CHECKPOINTING NODES are on block 341. If you aren't at this blockheight, close the wallet, open again, wait to resync. Our nodes are flooded with too many connections! New addnodes are coming!! A 32bit wallet dev ? The algo is very inefficient in 32 bit mode but we have included the code to compile in axiom-qt.pro if you like: DEFINES += USE_NUM_NONE USE_FIELD_INV_BUILTIN USE_SCALAR_INV_BUILTIN # 64-bit #DEFINES += USE_FIELD_5X52 USE_SCALAR_4X64 # 32-bit DEFINES += USE_FIELD_10X26 USE_SCALAR_8X32 Nevermind if I have to compile it as I dont know anything about compiling a wallet . I'll just move away from it in that case . We will compile one for you, please have some patience, and upgrade to a 64 bit OS soon Confirm Block 392NEW NODE:
addnode=162.222.181.215addnode=104.236.231.72 addnode=45.55.172.95 addnode=174.127.110.41 MORE NODES COMING anyone not at block 392, close wallet, reopen, wait to ask node fresh - we have many hundreds of connections to manage here! |
|
|
|
A lot of forks are happening. Diff is rising and we are adding two more strong nodes now. The nodes are in the DNS seeding and you can manually add: addnode=104.236.231.72 addnode=45.55.172.95 addnode=174.127.110.41 We will add 2 more servers quickly! If you have any problem compiling, make install: https://github.com/bitcoin/secp256k1i still fork with this nodes OFFICIAL CHECKPOINTING NODES are on block 341. If you aren't at this blockheight, close the wallet, open again, wait to resync. Our nodes are flooded with too many connections! New addnodes are coming!! A 32bit wallet dev ? The algo is very inefficient in 32 bit mode but we have included the code to compile in axiom-qt.pro if you like: DEFINES += USE_NUM_NONE USE_FIELD_INV_BUILTIN USE_SCALAR_INV_BUILTIN # 64-bit #DEFINES += USE_FIELD_5X52 USE_SCALAR_4X64 # 32-bit DEFINES += USE_FIELD_10X26 USE_SCALAR_8X32 A lot of forks are happening. Diff is rising and we are adding two more strong nodes now. NEW ADDNODESThe nodes are in the DNS seeding and you can manually add: addnode=104.236.231.72 addnode=45.55.172.95 addnode=174.127.110.41 addnode=162.222.181.215 We will add 2 more servers quickly! If you have any problem compiling, make install: https://github.com/bitcoin/secp256k1i still fork with this nodes OFFICIAL CHECKPOINTING NODES are on block 379. If you aren't at this blockheight, close the wallet, open again, wait to resync. Our nodes are flooded with too many connections! New addnodes are coming!! PRESS WINDOWS + R, ENTER:
notepad %APPDATA%/axiom/axiom.conf
ADD THIS TO THE FILE:
addnode=104.236.231.72
addnode=45.55.172.95
addnode=174.127.110.41
We're adding two more nodes now. Syncing is taking forever. If you have a node running with server=1 daemon=1 and youre around block 380, share your IP for addnode!
|
|
|
|
A lot of forks are happening. Diff is rising and we are adding two more strong nodes now. The nodes are in the DNS seeding and you can manually add: addnode=104.236.231.72 addnode=45.55.172.95 addnode=174.127.110.41 We will add 2 more servers quickly! If you have any problem compiling, make install: https://github.com/bitcoin/secp256k1i still fork with this nodes OFFICIAL CHECKPOINTING NODES are on block 379. If you aren't at this blockheight, close the wallet, open again, wait to resync. Our nodes are flooded with too many connections! New addnodes are coming!! PRESS WINDOWS + R, ENTER:
notepad %APPDATA%/axiom/axiom.conf
ADD THIS TO THE FILE:
addnode=104.236.231.72
addnode=45.55.172.95
addnode=174.127.110.41
We're adding two more nodes now. Syncing is taking forever. If you have a node running with server=1 daemon=1 and youre around block 380, share your IP for addnode!
|
|
|
|
|
Show Posts
