Topic: [ANN][KMD][dPoW] Komodo - An Open, Composable Smart Chain Platform, Secured by B - page 497. (Read 1192347 times)

Bittrex wallet is still under maintenance. Has anyone from the Komodo community been in contact with them? Missing out on staking rewards while they figure out their wallet issues. (yes, I'm well aware that this isn't Bittrex support - I just figured I'd ask here first)

ok but i have now a real issue when i start agama i get that error
 


my antivirus (kaspersky security 17) detected something as a thread i cleaned it up but this error showed up before
after i clicked on ok at that error the loading screen of agama daemon was showing up but nothing happened.
after this nothing happens when you get that error.

If you are interested about the technical details why Iguana was renamed to Agama you can read the following Slack post by Satinder:

i have found a little "bug" at the installation there still is "please wait until iguana gets installed" but i install agama

Yes, it will withdraw to whatever KMD address you have active. You must first change the KMD address through the 'home' tab.

The instructions are in OP:

How to send your KMD to an exchange

- go to 'home' tab
- click 'use exsisting KMD address'
- input the deposit KMD address you got from an exchange
- Now that you have the correct KMD address you can proceed to the 'payout' tab
- Since you are using a 3rd party address you don't have the seed, and thus you will click 'skip'
- Follow instructions and confirm the withdrawal

Warning: make sure you are doing the withdrawal to a correct address! Once we send out the KMD there is no way to retrieve it.

Those posts can be counted as low quality posts and Moderator won't hesitate when he sees them. I'm surprised how people spending their time on internet trolling around without purpose.
Im not en ICO iinvestor but i have bought it recently couse i think this is bargain price now, and i will wait for Komodo to wake up.
Evry coin resently had rise almost 100%, and those coins without any significance are interesting for whales? Strange situation. They probably waiting good oportunity for accumulation.
 

Hey Guys, can someone help me with the payout?

I want to send my KMD to Bittrex, but when I try to do the payout, there is always an address already entered, where the KMD are supposed to be sent to.

I don´t know where taht address points to. How can I change it?

Thank you very much!

for this reason you have to wait to 0.01

i fix all issues (also in node code too) and pool works very well now.
Komodo daemon in 2x faster now, nice work jl777!

i add port 6666 for big gpus rigs with max diff(16)
( !! NOT USE ZCASH ADDRESS to T-ADDRESS AND Z_ADDRESS !! )

HOW TO CONNECT
To mine KMD just use any ZCASH (EquiHash) miner with komodo address
example : ZecMiner64.exe -zpool komodominingpool.com:5555 -zwal komodo_address -zpsw x -allpools 1 ( Auto VarDiff - suitable for CPU and GPU )
example : ZecMiner64.exe -zpool komodominingpool.com:6666 -zwal komodo_address -zpsw x -allpools 1 (Max VarDiff - suitable for big GPUs RIG )

Happy mining komodo users
Cheers
 

payout created last week, not yet received 

ha! that's funny!

Very good returns, thanks to developers

Don´t feed the troll

I had to try few times just to success, even if you git clone, make git checkout "" , git pull, ... that's the only way I couldd fix this 

Since Komodo Native Mode is available for All major platforms (Winblows, OS X and Linux), I highly recommend on using Native Mode over other modes. Only use Basilisk Mode just in case you are impatient on downloading Blockchain.

And those who might have trouble sending transactions via Basilisk Mode in recent weeks should be aware that we had been dealing with Blockchain event. And Basilisk Mode depends on Notary Nodes. Whenever Notary Nodes are updating with latest Komodo versions and fixing blockchain, Basilisk Mode will either be slow or not responsive. Now that we are getting on more stable and solid network than before such issues should be expected to be lesser.

In case you are having issues with Native Mode may be doing resync of Komodo Blockchain might be helpful. You can try that by deleting blockchain data from Komodo Data Directory and just keeping your wallet.dat and komodo.conf there, and then start Native Mode in Agama Desktop Wallet.

You'll be deleting these files and directories only from Komodo Data directory:


You can find Komodo Data directory for your OS at:
Linux: ~/.komodo/
OSX: ~/Library/Applications Support/Komodo/
Windows: %AppData%/Komodo/

I should warn NOT to delete your Assetchains and PAX folders there. Those have your individual wallet.dat for them.

Linux and OSX data directory will be hidden from Finder/File Explorers. So, find your ways to get to these hidden directories and clean the data.

Hope this helps.

For better and realtime support please join our SuperNET Slack. (http://slackinvite.supernet.org)

It sounds like you have some edge case bug. There are so many variables in play that it takes time to iron out all of them. For example, recently we fixed a bug that was present in on out of ~500 KMD addresses.

If you would be so kind to join our Slack and report the bug in more detail. Alternatively go to 'view' and then 'toggle developer tools' and select 'console'. Then try to send a transaction again, take a screenshot and PM me all the details including your operating system.

Because of these cases we recently came up with a temporary solution where you run Agama from a live USB stick or CD. See the guide below:

How to Run Agama From a Ubuntu 16.04 Bootable USB Drive

this looks like a different error, so some progress.

are you sure z-nomp is configured correctly?
127.0.0.1:8232 is not a KMD port
also KMD doesnt mine to z-addresses, it mines to transparent addresses, so not sure why it is looking for operation ids.

My guess is that the nomp isnt quite matched up. movetocrypto should be able to help you

Again....

2017-03-26 00:22:47 [Payments]   [komodo] Error with payment processing daemon {"type":"offline","message":"connect ECONNREFUSED 127.0.0.1:8232"}
2017-03-26 00:22:49 [Payments]   [komodo] Unable to get operation ids for clearing.

error in this point ( z_getoperationstatus )
z-nomp/libs/paymentProcessor.js

377-384
       daemon.cmd('z_getoperationstatus', null, function (result) {
          if (result.error) {
            logger.warning(logSystem, logComponent, 'Unable to get operation ids for clearing.');
          }
          if (result.response) {
            checkOpIdSuccessAndGetResult(result.response);
          }
       }, true, true);
    }, opid_interval);

I've been trying for weeks to get some Komodo I purchased/mined onto an exchange but I am having no luck.  I have tried so many different versions of the Iguana/Agama app on both Windows and Mac and I can never get a transaction to send.  It always get stuck at transmitting transaction and then eventually takes me back to the activate coin screen.  I have been trying for weeks to send a transaction.  I've tried refreshing balances right before sending and every other piece of advice I have seen.  What am I missing?

KMD / BTC market is paused

Trading is currently disabled, please contact Cryptopia Support if you have and questions.


Does anybody know why ? Is it a Komodo or just a Cryptopia problem ?