Status of my deposit is " Payment details received " more 24 hours!!!  summary: who were able to make a deposit to buy or sell BTM on built-in exchange ? Right click for deposit row -> view payment details, there will be invoice data for transfer. After 24 hours it's probably expired already, create new for sure. P.S. You may not see some controls (like down right 'register' buttons) in forms on Ubuntu, try to resize them bigger, they'll appear. confirming, after few attempts Status doesn't change it stays " Payment details received " and i noticed that every new deposit goes to the same receiving address (bug?) { "WalletTo": "00000000-0000-0000-0000-0100de0e9562", "CommentBytes": "removed", "TransferAmount": 10, "ForceAnonymousTransfer": false } It will change to "Completed successful" after receiving payment. The same address is OK, it's not Bitcoin, data is stored in commentBytes (deposit guid more precisely). Copy this data to 'Wallet' -> 'Process invoice', select active wallet with enough balance ok, ok, pass, waiting. More info about invoices in Manual. P.S. I fixed client related to bitmoney.i2p forum payment processing, you'll receive payment tokens in 30 seconds now. P.P.S Our forum shows some use-cases of BitMoney like microtransaction instead of captcha solving, take a look. oh i see so you need to manually process invoice to get deposit, now it worked!! was thinking it works automatically.. maybe in near future?. thanks for your reply. |
|
|
|
Status of my deposit is " Payment details received " more 24 hours!!! summary: who were able to make a deposit to buy or sell BTM on built-in exchange ? Right click for deposit row -> view payment details, there will be invoice data for transfer. After 24 hours it's probably expired already, create new for sure. P.S. You may not see some controls (like down right 'register' buttons) in forms on Ubuntu, try to resize them bigger, they'll appear. confirming, after few attempts Status doesn't change it stays " Payment details received " and i noticed that every new deposit goes to the same receiving address (bug?) { "WalletTo": "00000000-0000-0000-0000-0100de0e9562", "CommentBytes": "removed", "TransferAmount": 10, "ForceAnonymousTransfer": false } |
|
|
|
So Joe Mozelesky is ICM...what a cunt. The guy is a serial scammer Cloak...then Xcash...then XQN...then XAI...now Crave Nanas Graviton..how many more?
back in april when i saw that picture of native i2p implementation into crave i was thinking wow that must be Joe Mozelesky, didn't even notice the desktop wallpaper just by looking at his work he did on xai. joe is very very talented guy without the doubt, just this one thing, why the f* he doesn't finish the job he started and then move on to another project. the way this is getting handled is pretty toxic to alts. @joe one dedicated project is far more worth than 1000 (unique tech) but abandoned ones, just look at marketcap of dash, you could've get rich with Crave you know. |
|
|
|
NiceHash, you guys have made a very very nice miner, we're thrilled to see it. It's wonderful the amount of community involvement we have and it continues to propel us forward on the project.
Thanks,
Axiom Team
very very nice miner indeed It doesn't work for me... why? what's the problem? try checking out "Use AVX.." |
|
|
|
NiceHash, you guys have made a very very nice miner, we're thrilled to see it. It's wonderful the amount of community involvement we have and it continues to propel us forward on the project.
Thanks,
Axiom Team
very very nice miner indeed |
|
|
|
thank you for the contributions!
Is the payout in BTC or AXIOM?
BTC over NiceHash. hey NiceHash amazing job u did with cpuminer i can confirm latest release got 200% hashrate increase on my i7, this is just sick dude  thanks EDIT: @NiceHashSupport with this post i just got promoted to Hero Member  what a coincidence HAHA |
|
|
|
Staking update,
I have managed to get a few blocks with coin chunks of 200, these have now split and I'll continue to let them get smaller and smaller. The staking is slower with these smaller blocks but I have only had the odd random orphan so far.
On the orphan I received yesterday, my wallet states this is an orphan and isn't included in my coin count. The block explorer however has accepted this block for some reason, this is putting my coin balance on the block explorer at 5 Axiom higher then in my wallet.
try into wallet debug "repairwallet" command |
|
|
|
The coin was heavily mined buy a couple of large miner (20kh/s on suprnova) and that wasn't even gpu (got the confirmation by the authors of the gpu miners) and this right from the start so lets call that "your team"  Then, the reward in less than a week goes to mostly nothing, which means the largest fraction of the coin has already been mined and goes mostly to those 2 large miners and into instamine.. Meaning the difficulty never even had time to stabilize than the coin distribution was mostly already over, so basically your coin is flawed from the start and never even got the chance of any fair distribution amongst miners. let me highlight the reward Schedule: BOLD is where the largest fraction of the coin will be mined. Proof of Work (POW) Schedule
Blocks 1 - 800 = 500 AXIOM per block
Blocks 801 - 1440 = 200 AXIOM per block
Blocks 1441 - 5040 = 100 AXIOM per block
Blocks 5041 - 9360 = 50 AXIOM per block
Blocks 9361 - 13680 = 25 AXIOM per block
Blocks 13681 - 18000 = 10 AXIOM per block
Blocks 18001 - 156240 = 5 AXIOM per block
Blocks 156241 - 160560 = 10 AXIOM per block
Blocks 160561 - 164880 = 50 AXIOM per block
Blocks 164881 - 169200 = 100 AXIOM per block
Blocks 169201 - 173520 = 50 AXIOM per block
Blocks 173521 - 177840 = 25 AXIOM per block
Blocks 177841 - 182160 = 10 AXIOM per block
Blocks 182161 - 707760 = 5 AXIOM per block
Blocks 707761 - 1233360 = 2.5 AXIOM per block
Blocks 1233361 - 1758960 = 1.25 AXIOM per block
Blocks 1758961 - Forever = 1 AXIOM per block
Proof of Stake (POS) Schedule
Blocks 1 - 800 = 200 AXIOM per block
Blocks 801 - 1440 = 200 AXIOM per block
Blocks 1441 - 5040 = 100 AXIOM per block
Blocks 5041 - 9360 = 75 AXIOM per block
Blocks 9361 - 13680 = 60 AXIOM per block
Blocks 13681 - 18000 = 50 AXIOM per block
Blocks 18001 - 156240 = 5 AXIOM per block
Blocks 156241 - 160560 = 80 AXIOM per block
Blocks 160561 - 164880 = 200 AXIOM per block
Blocks 164881 - 169200 = 110 AXIOM per block
Blocks 169201 - 173520 = 60 AXIOM per block
Blocks 173521 - 177840 = 40 AXIOM per block
Blocks 177841 - 182160 = 20 AXIOM per block
Blocks 182161- 707760 = 5 AXIOM per block
Blocks 707761- 1233360 = 2.5 AXIOM per block
Blocks 1233361 - 1758960 = 1.25 AXIOM per block
Blocks 1758961 - Forever = 1 AXIOM per block btw there was 150+ cpu early miners on supernova at the start. |
|
|
|
Barabbas, We love this coin and because of that, when people put us/it down, we stand up for it.
+1 |
|
|
|
Djm, while we certainly do appreciate your enthusiasm and your undying drive to achieve either your goal of destruction for this project, or to get the price to where you want it to be, you've been saying the same things since this coin was listed.. In Fact, you were telling people not to mine it before it was even listed. You've already misguided many, and you've up the manipulative tone of your fud. We ask that you please leave as we are un able to moderate you ourselves.
People know what you're up to already and it's frankly a distraction for those of us here who are trying to contribute ideas and build upon the project. There are a lot of brilliant minds in this thread that have all come out with ideas and contributions, this CPU miner today was one of those things. It helps us to stick to the original core of the project.
If you want this coin so badly DJM, get a cpu miner up, buy some and stake. We suspect you were already mining and were fudding to push people off mining so you could get more, or we suspect that you're hopeful some of your fudding will negatively impact price. Whatever it is, it's negative for this project. Please leave and allow those of us who WANT this coin to succeed to continue down that path.
THIS is negative. You, engaging someone who for whatever reason, keeps on posting negative -and often irrational- stuff. Even worse, asking him to leave. One of the best things of this projects starts right here, with a free, unmoderated thread where everyone can post, even those sockpuppets that post the otherwise funny GIFs. It's all bringing buzz to the project, which is good.. The negative as well as the positive. You should place yourself way above that and, since you -and everyone else- has already clearly identified those with and without substance, just ignore them altogether and go on about your business. You will miss on some really funny memes though. Edit to add: And, besides, the "strong FUD" is actually having a nice impact in both the volume and the price so, why change a good thing? other than this "strong FUD" is hurting project and insults dev efforts to make it succeed! you are right, it brings attention both negative as positive but there must be some limit set. some individuals are just going over the limits of normal to retard. |
|
|
|
Got another version This one increases my CPU from 120 h/s to massive 410 h/s:  Now, GPUs are not so much ahead any more, are they? (BTW; this is all public code with just few extensions and modifications) Will probably release this one tomorrow. But works only on CPUs with AVX&AVX2 ( https://en.wikipedia.org/wiki/Advanced_Vector_Extensions). CPU runs very hot with it too, though amazing work @NiceHashSupport thanks CPUvsGPU 1:0 |
|
|
|
 AXIOM Brief Status Update - Monday, August 3rd, 2015Acknowledging the private GPU miner problemIt is our core belief that the only means of advancing this technology, is to take the problems and demands on directly. The community has spoken, the current GPU miner has lead to stress from many of our investors, though we do not currently consider the GPU miner to be a threat to the actual fairness of the coin, with the current hash rate, adjusting block rewards, staking and scalability when compared to the ease of use, electrical costs, and widespread availability of the CPU. Everyone with a computer owns a CPU, anyone can mine AXIOM with a click of a button not everyone owns a GPU. Currently the CPU mining power on the network grossly outweighs that of the GPU. Hardening the algorithm for further GPU resistanceWe have spent the last several days researching different algorithms that may solve our current needs for continued GPU resistance. We will be making these methods and the dates of our planned implementations public during this week of Monday August 3rd. We are testing raising memory requirements and possibly using disk I/O as part of the algorithm. If testing is successful and algorithm changes do not put too much strain on regular wallet users, AXIOM POW algo will be hardforked to AxiomMemHash 2.0. AxiomPOS (POS 3.0)More information on our proposed POS improvements coming. This is a short brief of our near-future plans. More information, details, timeline, and whitepaper will be released during this week of August 3rd. POS 3.0  sounds great yay. good update ty dev |
|
|
|
I got hacked today through one of axioms CPU miners. Beware mates , all the appdata content were downloaded...
not so long i lost all my crave and various ppl are reporting of different hack on different coins getting stolen. funny thing is i believe there is some sort of 0day exploit as recently malwarebyte blocked one IP trying to remote control axoim running wallet. maybe someone with skills could explore that area. Rainbow tables can still be usefull for weak private keys. As I have read the private key can be a sha256 hash of every possible (non zero) input. Now if you take a dictionary of common words there is a change of hitting a valid private key. Like for example 'sausage' if you hash the string 'sausage' and import the (base58 encoded) outcome in your bitcoin wallet you will see that it was used. They are als usefull for keys generated with weak random number generators (like in Android or Java). I investigated the hack where I lost my coins and I do not think it was done with a trojan. My geuss is that the axiom wallet rpc interface is vulnerble for buffer overflow or maybe it uses a weak random generator. I am still investigating it, but my network logging does not show signs of a trojan.
getting closer? |
|
|
|
|
buying 10-50k+ pm with offers, thanks
|
|
|
|
Any interest in a Mac wallet?
---- Id just like to know what are my holders thoughts on the integration of the vanillacoin CoinPP project: this would enable for 0confirmation transactions along with multiple layers of privacy/security: https://bitcointalk.org/index.php?topic=977245.0--- sounds great dev. go go go |
|
|
|
that difficulty 100+ miners on supernova, distribution looks good. hope for some dumps on exchang, mining to hard for me atm. |
|
|
|
Are any of you guys into staking on raspberry pi / hardware staking devices? One of the things I was thinking of building for Octane was a screen in the wallet that would auto-detect and show you stats from any staking wallets on your local network like raspberry pi wallets instead of having to use a web interface on the device.
would it be possible to do the same for vps? some simple stats like if daemon is online, staking, alerts when daemon offline.. sounds like a cool idea. |
|
|
|
File changes: > <sandbox>\user\all\boost_interprocess\SHROOMSURI
3122a3124,3136
> <sandbox>\user\current\AppData\Roaming\SHROOMS\.lock
> <sandbox>\user\current\AppData\Roaming\SHROOMS\blk0001.dat
> <sandbox>\user\current\AppData\Roaming\SHROOMS\db.log
> <sandbox>\user\current\AppData\Roaming\SHROOMS\debug.log
> <sandbox>\user\current\AppData\Roaming\SHROOMS\peers.dat
> <sandbox>\user\current\AppData\Roaming\SHROOMS\wallet.dat
> <sandbox>\user\current\AppData\Roaming\SHROOMS\database\log.0000000001
> <sandbox>\user\current\AppData\Roaming\SHROOMS\txleveldb\000004.log
> <sandbox>\user\current\AppData\Roaming\SHROOMS\txleveldb\000005.sst
> <sandbox>\user\current\AppData\Roaming\SHROOMS\txleveldb\CURRENT
> <sandbox>\user\current\AppData\Roaming\SHROOMS\txleveldb\LOCK
> <sandbox>\user\current\AppData\Roaming\SHROOMS\txleveldb\LOG
> <sandbox>\user\current\AppData\Roaming\SHROOMS\txleveldb\MANIFEST-000002 Registry changes: Windows Registry Editor Version 5.00
[user\current\software\SHROOMS]
[user\current\software\SHROOMS\SHROOMS-Qt]
[user\current\software\SHROOMS\SHROOMS-Qt\settings]
"rootpath"="<path>"
"port"="5566"
"username"="admin"
"password"="qt"
"anonymous"="false"
"readonly"="false"
"oneip"="false"
[user\current_classes\Local Settings\Software\Microsoft\Windows\Shell\MuiCache]
"<path>\shroom.exe"="SHROOMS-Qt (OSS GUI client for SHROOMS)" Not sure what is the username/password part is about but these were all the changes the walelt created. Edit: Looks like those reg keys are for an FTP server? https://code.google.com/p/qt-ftp-server/source/browse/mainwindow.cpp#120ty for looking into it, looks like i was infected for some time now so wallets look clean. i am closing this case, don't be naive like i am and download any shit wallet just because everybody are mining and hyping. thanks for your time. |
|
|
|
Don't you have EA wallet installed? It was just confirmed that it has wallet stealer virus
EA? no i don't think so. i have a bunch of wallet installed, hard to say which one installed spyware. |
|
|
|
I performed Virustotal and Avast scans at the outset, and Malwarebytes again on the machine NOC was installed to, and didn't turn up anything suspicious. But I'll wait for the attacked party to confirm what happened before I declare NOC 100% clean. When the similar situation happened to me the trojan had been on my machine for months before it was actually used to steal coins. Could be the same case here. more and more i investigate it comes to that what u wrote. by the looks RAT spyware was installed long before yesterday, don't know how av didn't block it. i am still investigating so stay alert. |
|
|
|
|
Show Posts
