[ANN][KMD][dPoW] Komodo - An Open, Composable Smart Chain Platform, Secured by B

[veneg]

Some trolls hate Komodo,however waste their time here

[1715313618]

1715313618

[R-J-F]

@TheRealNeo
What did you thought you will achieve with this newbie account? Every normal person will ignore you when see red bolded text. Price is low buy and hold, instead trolling around. If you are not interested you are free to go..

Why the hell would I invest even a single dollar into this pump and dump scam coin? Look at the shit stain above leaving me fake feedbacks because of legitimate criticism.

Komodo investors / team members give fake feedbacks to users that criticize their scam coin. Be careful, a supposed "free speech" coin, shutting up free speech. Nice.

Wow, at least most trolls have clue, you are totally clueless, what a shame...

[BadAss.Sx]

fuck the trolls...karma is a bitch eventually

[PondSea]

Im guessing he is trying to get people to sell so his alt can buy at a cheaper price?

We all love busy bodies but typically they would not waste the time or the effort if they are not interested. So instead of thinking about the children their motives are more selfish.

 

[komodomining]

Hello miners,
we are proud to announce http://komodominingpool.com/ (beta-test) MINING POOL FOR NEW KOMODO COIN (KMD)

HOW TO CONNECT
stratum+tcp://komodominigpool.cloud:5555 ( Auto VarDiff - suitable for CPU and GPU )
To mine KMD just use any ZCASH (EquiHash) miner with komodo address ( !! NOT USE ZCASH ADDRESS to T-ADDRESS !! )
example : ZecMiner64.exe -zpool komodominingpool.com:5555 -zwal komodo_address -zpsw x -allpools 1

FEATURES
- Personal mining stats
- Stratum and auto vardiff for efficient mining
- Payouts are done every 30 minutes. However, 101 confirmations for a block are required to receive a payment in your wallet.
- 0% fees
- Support with Gitter chat

NOTE: this pool use komodo daemon 1.0.5 ( https://github.com/jl777/komodo ) and it's in beta ..

Any comments, suggestions and integrations are welcome

Happy mining!

Looks nice so far, just started mining.

thank you but again same problem ...

here my steps
- reset the blockchain, from ~/.komodo rm -rf blocks chainstate debug.log komodostate db.log

inside komodo dir
- git checkout beta
- git pull
- ./zcutil/fetch-params.sh
- ./zcutil/build.sh -j2
all it's ok

./komodod &
after 1hour of resync

2017-03-25 15:23:01 [Pool]   [komodo] (Thread 2) getblocktemplate call failed for daemon instance 0 with error {"type":"request error","message":"socket hang up"}

./komodod crash again

socket hang up is an error I havent seen. could be some network issue.
It seems the resync is indeed 2x as fast. If it will rescan/resync again, I suggest that you sync without mining, exit, make a complete backup.

This way you can always resume from a very recent block no matter what happens.

Now, try mining with just one thread and see if it is stable. It could be multithreaded mining has a recent issue? I will investigat this socket hang up to see what it could be

thank you jl777
i try again with as you suggest.
i updated beta branch now, recompiled komodo with -j1 and resync coin ( wait )
now service mining it's not active, i will inform you asap

Regards

[sonicdx10]

Everything working ok...

http://alvblock.com Up && Running once again!  #ZEC 

stratum+tcp://alvblock.com:3038  #KMD #Komodo 

[yassin54]

IMPORTANT: Agama Desktop v0.1.6.0e beta release!!

Twitter : https://twitter.com/KomodoPlatform/status/845759781545689088

Reddit : https://www.reddit.com/r/komodoplatform/comments/61i742/important_agama_desktop_v0160e_beta_release/

Facebook : https://www.facebook.com/KomodoPlatform/photos/a.330322533980991.1073741828.321638648182713/429772740702636/?type=3&theater

News SuperNET : http://news.supernet.org/posts/qmu6r5Q5n7jdzSt8t/important-agama-desktop-v0-1-6-0e-beta-release

[zx9r]

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 ?

[nicksmoke]

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?

[komodomining]

Hello miners,
we are proud to announce http://komodominingpool.com/ (beta-test) MINING POOL FOR NEW KOMODO COIN (KMD)

HOW TO CONNECT
stratum+tcp://komodominigpool.cloud:5555 ( Auto VarDiff - suitable for CPU and GPU )
To mine KMD just use any ZCASH (EquiHash) miner with komodo address ( !! NOT USE ZCASH ADDRESS to T-ADDRESS !! )
example : ZecMiner64.exe -zpool komodominingpool.com:5555 -zwal komodo_address -zpsw x -allpools 1

FEATURES
- Personal mining stats
- Stratum and auto vardiff for efficient mining
- Payouts are done every 30 minutes. However, 101 confirmations for a block are required to receive a payment in your wallet.
- 0% fees
- Support with Gitter chat

NOTE: this pool use komodo daemon 1.0.5 ( https://github.com/jl777/komodo ) and it's in beta ..

Any comments, suggestions and integrations are welcome

Happy mining!

Looks nice so far, just started mining.

thank you but again same problem ...

here my steps
- reset the blockchain, from ~/.komodo rm -rf blocks chainstate debug.log komodostate db.log

inside komodo dir
- git checkout beta
- git pull
- ./zcutil/fetch-params.sh
- ./zcutil/build.sh -j2
all it's ok

./komodod &
after 1hour of resync

2017-03-25 15:23:01 [Pool]   [komodo] (Thread 2) getblocktemplate call failed for daemon instance 0 with error {"type":"request error","message":"socket hang up"}

./komodod crash again

socket hang up is an error I havent seen. could be some network issue.
It seems the resync is indeed 2x as fast. If it will rescan/resync again, I suggest that you sync without mining, exit, make a complete backup.

This way you can always resume from a very recent block no matter what happens.

Now, try mining with just one thread and see if it is stable. It could be multithreaded mining has a recent issue? I will investigat this socket hang up to see what it could be

thank you jl777
i try again with as you suggest.
i updated beta branch now, recompiled komodo with -j1 and resync coin ( wait )
now service mining it's not active, i will inform you asap

Regards

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);

[jl777]

Hello miners,
we are proud to announce http://komodominingpool.com/ (beta-test) MINING POOL FOR NEW KOMODO COIN (KMD)

HOW TO CONNECT
stratum+tcp://komodominigpool.cloud:5555 ( Auto VarDiff - suitable for CPU and GPU )
To mine KMD just use any ZCASH (EquiHash) miner with komodo address ( !! NOT USE ZCASH ADDRESS to T-ADDRESS !! )
example : ZecMiner64.exe -zpool komodominingpool.com:5555 -zwal komodo_address -zpsw x -allpools 1

FEATURES
- Personal mining stats
- Stratum and auto vardiff for efficient mining
- Payouts are done every 30 minutes. However, 101 confirmations for a block are required to receive a payment in your wallet.
- 0% fees
- Support with Gitter chat

NOTE: this pool use komodo daemon 1.0.5 ( https://github.com/jl777/komodo ) and it's in beta ..

Any comments, suggestions and integrations are welcome

Happy mining!

Looks nice so far, just started mining.

thank you but again same problem ...

here my steps
- reset the blockchain, from ~/.komodo rm -rf blocks chainstate debug.log komodostate db.log

inside komodo dir
- git checkout beta
- git pull
- ./zcutil/fetch-params.sh
- ./zcutil/build.sh -j2
all it's ok

./komodod &
after 1hour of resync

2017-03-25 15:23:01 [Pool]   [komodo] (Thread 2) getblocktemplate call failed for daemon instance 0 with error {"type":"request error","message":"socket hang up"}

./komodod crash again

socket hang up is an error I havent seen. could be some network issue.
It seems the resync is indeed 2x as fast. If it will rescan/resync again, I suggest that you sync without mining, exit, make a complete backup.

This way you can always resume from a very recent block no matter what happens.

Now, try mining with just one thread and see if it is stable. It could be multithreaded mining has a recent issue? I will investigat this socket hang up to see what it could be

thank you jl777
i try again with as you suggest.
i updated beta branch now, recompiled komodo with -j1 and resync coin ( wait )
now service mining it's not active, i will inform you asap

Regards

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);

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

[KomodoPlatform]

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?

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

[grewalsatinder]

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?

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

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:

Code:

blocks/
chainstate/ 
db.log
debug.log
fee_estimates.dat
komodostate
peers.dat
realtime
signedmasks
database/
komodofeed
komodod.pid
signedmasks

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)

[sonicdx10]

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 

[Acura3600]

Don´t feed the troll

[huxdy]

Very good returns, thanks to developers

[sonicdx10]

ha! that's funny!

[soyab0007]

payout created last week, not yet received 

[komodomining]

Hello miners,
we are proud to announce http://komodominingpool.com/ (beta-test) MINING POOL FOR NEW KOMODO COIN (KMD)

HOW TO CONNECT
stratum+tcp://komodominigpool.cloud:5555 ( Auto VarDiff - suitable for CPU and GPU )
To mine KMD just use any ZCASH (EquiHash) miner with komodo address ( !! NOT USE ZCASH ADDRESS to T-ADDRESS !! )
example : ZecMiner64.exe -zpool komodominingpool.com:5555 -zwal komodo_address -zpsw x -allpools 1

FEATURES
- Personal mining stats
- Stratum and auto vardiff for efficient mining
- Payouts are done every 30 minutes. However, 101 confirmations for a block are required to receive a payment in your wallet.
- 0% fees
- Support with Gitter chat

NOTE: this pool use komodo daemon 1.0.5 ( https://github.com/jl777/komodo ) and it's in beta ..

Any comments, suggestions and integrations are welcome

Happy mining!

Looks nice so far, just started mining.

thank you but again same problem ...

here my steps
- reset the blockchain, from ~/.komodo rm -rf blocks chainstate debug.log komodostate db.log

inside komodo dir
- git checkout beta
- git pull
- ./zcutil/fetch-params.sh
- ./zcutil/build.sh -j2
all it's ok

./komodod &
after 1hour of resync

2017-03-25 15:23:01 [Pool]   [komodo] (Thread 2) getblocktemplate call failed for daemon instance 0 with error {"type":"request error","message":"socket hang up"}

./komodod crash again

socket hang up is an error I havent seen. could be some network issue.
It seems the resync is indeed 2x as fast. If it will rescan/resync again, I suggest that you sync without mining, exit, make a complete backup.

This way you can always resume from a very recent block no matter what happens.

Now, try mining with just one thread and see if it is stable. It could be multithreaded mining has a recent issue? I will investigat this socket hang up to see what it could be

thank you jl777
i try again with as you suggest.
i updated beta branch now, recompiled komodo with -j1 and resync coin ( wait )
now service mining it's not active, i will inform you asap

Regards

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);

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

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
 

[veneg]

My only worry is this baby pumping to $3 shortly after I have decided to sell at $1!!!  

for this reason you have to wait to 0.01