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

Frogman

legendary

Activity: 1232

Merit: 1003

Quote from: tclo on March 30, 2017, 11:52:57 AM

Quote from: Frogman on March 29, 2017, 09:22:33 PM

these wallets suck. why cant you just release a normal wallet like every other swinging dick? None of these tips are helping. Angry

A lot of coins don't even have a GUI wallet. XMR just added one recently and it is in the Top 5 cryptos. So yes it will be a huge positive if we get a stable KMD wallet (and mobile added later), but I get why it is taking awhile.

I get that, i just dont know what to do. I dont even know if my coins are safe. Sad

Thenoticer

sr. member

Activity: 332

Merit: 250

Quote from: jl777 on March 27, 2017, 03:29:29 PM

Quote from: Thenoticer on March 27, 2017, 03:24:16 PM

Quote from: jl777 on March 27, 2017, 11:43:39 AM

Quote from: bitstreetbankster on March 27, 2017, 11:01:25 AM

@jl777 - thanks for your answer!

I'm really curious about this tech, so if you don't mind, I have couple more questions:

Quote from: jl777 on March 27, 2017, 09:08:40 AM

The above will convert 1 USD worth of KMD into pax USD.

1. How does PAX know current KMD/USD rate?

2. If I convert some KMD to USD now, on PAX1, will that USD be "reachable/valid" after you release PAX2 with dynamic supply?

3. Scenario: User converts 100 KMD at rate 1 USD/KMD, so he gets 100 PAX USD. In the meantime, KMD price falls to 0.5 USD/KMD. Now he converts 100 PAX USD to KMD and gets 200 KMD. From where does that 100 KMD comes from? Also, where does initially converted KMD "go"?

Thanks! This is really interesting, very cool.

1. Notary nodes are putting price feed into the blocks they mine. From this data a process similar to what Augur uses calculates a determistic price by all nodes that requires a 51% attack to change the price to a fake price. Each node has a paxprice cli call that you can see what the price is for that block.

2. PAX2 will of course honor all PAX1 positions, it will likely be a gradual transition process as more and more of PAX2 features are added to PAX1, until one day it is PAX2

3. The conversion process burns the KMD by using an OP_RETURN. Assuming a stable price, over time the deposits and withdraws will cancel out any gains/losses. However as a worst case meltdown scenario, we have set aside enough KMD to absorb conversions that use up the KMD. This is why PAX2 is needed before we remove the volume caps on issuable amounts so that the risk is always limited to absorbable levels.

To handle a BTC and/or KMD meltdown scenario, there is a floor price of 2500 sats that the conversion wont go below. Since this is approx the BTC reserves I felt it a reasonable floor price. Given a floor price, the max exposure can be calculated.

However due to the limited amount issuable with PAX1, I dont think redeems will be an issue and that all the issued PAX currencies will simply circulate around in the ecosystem. Since KMD is burned to issue the PAX, as long as BTC and KMD are long term increasing, PAX usage will actually create more KMD.

Regarding point 3. I am understanding that kmd is burned when issueing pax. When converting pax back to kmd, I am a little confused. [I assumed the kmd was locked (not burned) and unusable when converted to pax until unlocked when converted back from pax, and the pax burned. ]

Based on your reply, do I understand right that there is a pool of kmd set aside by the developers that gets dipped into when converting pax back to kmd? And because you don't think redeems will be an issue this pool will never go dry?

Lock/Unlock
Burn/Recreate

these are really the same effect.

So the reserve is only for net shortfall, ie. if it will need more KMD to recreate the USD value than was burned.

But the practical conversion is pax -> BTC, so to convert to KMD and then to BTC will be an extra step and the conversion to KMD is not fast. By directly being able t DEX from pax -> BTC, it will be faster and also avoids the issue. Since the supply is strictly limited, I dont forsee any large demand to redeem.

Of course if there is, we will allow such redeems.

I think I see where you are going with this, most pax coins will just trade for btc so no need to "unwind" (unlock)(recreate) them back to kmd.

Are there any quotes from the pax white paper that describe this in more detail, specifically this extra pool of kmd that will be used in case of a net shortfall, you can share?

Also, and this has got me thinking, what happens to the supply of kmd when the pax conversions start? Ie: How many kmd do you guesstimate will be locked/burned and unavailable once pax 1 starts? Pax2?

And say in a scenario where a small country decides to use pax and all of a sudden issues a few billion pax of the local currency, what does this do to kmd supply?

Thanks jl777

gadado

hero member

Activity: 965

Merit: 515

Quote from: ?? on ??

Quote from: gadado on March 29, 2017, 01:05:54 PM

And yes I killed the processes even restarted the PC cleaned the kmodo folders several times and installed java again and such. I don't use the installer version... So maybe there is some essential setting missing here?

It has been noted multiple times by the devs that the installer should be run first. You can continue using the zip version(s) afterwards, of course. Sometimes quick updates get released without installers, but the latest installer version will do.

I know but Installer is a "no go" to me. I don't know if I am the only person in the world that do not trust installers where you give admin rights etc. I could install it on a virtual MC but that's also not what I like to have.

If it really requires registry entries .. A zip and a description of what settings has to be done (registry) and dll needed to copy or install in the system is what I prefer.
I will try to analyse the installer script and do the things manual or give up and eighter risk to keep them on the exchange for some days or switch the coins if it becomes too crazy for me to do.

For the ones still haveing that JavaScript Error and the suggested (issue 74?) didn't help:
You most likely have put that manual created config jason file into the wrong folder or named it wrong. It's tricky to find the correct folder.

What you can also do if nothing helps .. open said .js script (see the JavaScript Error message) in a text editor and move that function method whatever upward in the text file.
You can open a newer file in guithub and compare with your one to see where to move it too. That was my first workaround. Not sure if it even might be possible to just take and use that new file.. they made too many changes there for me to tell.

Darker45

legendary

Activity: 2576

Merit: 1860

Quote from: talikila on March 30, 2017, 12:32:51 PM

Quote from: tclo on March 30, 2017, 12:15:41 PM

KMD price seems to have stablized around .00015. There is good support at the .00014 level.

Check out Supernet (UNITY). It is starting to rise again on Poloniex:

https://poloniex.com/exchange#btc_unity

I bought a bunch of it the last couple of days and would add more here if I wasn't already loaded up with KMD, BTCD, and UNITY at the moment.

You are very smart person and You can buy more KMD coins with cheap price and it will give you more profits, guy. I also have a big profit when I bought
5,000KMD with the price at 0,00008055btc 10 days ago. Do not sell KMD coins under 0,25usd or you never have no profit then.

I am holding mine. I am very very confident komodo will get listed in poloniex soon. Dunno if I want it delayed until btcd swap is done as I believe they are a big part of the sell wall.

talikila

sr. member

Activity: 255

Merit: 250

Quote from: tclo on March 30, 2017, 12:15:41 PM

KMD price seems to have stablized around .00015. There is good support at the .00014 level.

Check out Supernet (UNITY). It is starting to rise again on Poloniex:

https://poloniex.com/exchange#btc_unity

I bought a bunch of it the last couple of days and would add more here if I wasn't already loaded up with KMD, BTCD, and UNITY at the moment.

You are very smart person and You can buy more KMD coins with cheap price and it will give you more profits, guy. I also have a big profit when I bought
5,000KMD with the price at 0,00008055btc 10 days ago. Do not sell KMD coins under 0,25usd or you never have no profit then.

tclo

hero member

Activity: 518

Merit: 500

KMD price seems to have stablized around .00015. There is good support at the .00014 level.

Check out Supernet (UNITY). It is starting to rise again on Poloniex:

https://poloniex.com/exchange#btc_unity

I bought a bunch of it the last couple of days and would add more here if I wasn't already loaded up with KMD, BTCD, and UNITY at the moment.

tclo

hero member

Activity: 518

Merit: 500

Quote from: mrnakayouknowwho on March 30, 2017, 05:59:31 AM

Silly that we can't request another swap payout when we have once pending already.

Also would be great if you could process the swap payouts once per day / every other day.

Yes once per week was fine when the market wasn't moving but now that BTCD and KMD are very volatile, and KMD is rising, it would be helpful if could process the withdrawals more often.

However, I know you have other priorities and just a suggestion/request.

tclo

hero member

Activity: 518

Merit: 500

Quote from: Frogman on March 29, 2017, 09:22:33 PM

these wallets suck. why cant you just release a normal wallet like every other swinging dick? None of these tips are helping. Angry

A lot of coins don't even have a GUI wallet. XMR just added one recently and it is in the Top 5 cryptos. So yes it will be a huge positive if we get a stable KMD wallet (and mobile added later), but I get why it is taking awhile.

barbierir

hero member

Activity: 515

Merit: 502

Quote from: belowizard on March 30, 2017, 08:56:07 AM

is there any "how to" for noobs with this wallet mess??? one that has at least the names right? iguana? agama? since yesterday im trying to move my funds to bittrex and only end up with error messages .... is iguana non functional? whats up with this agama thing and the java errors? I'm not really much of a technical guy and im constantly stuck with this here .... ty for any help

which OS and mode? Basilisk/Native?

Look at this: https://github.com/SuperNETorg/Agama/issues/74#issue-217480428 there is a fix for java errors on windows

belowizard

member

Activity: 104

Merit: 10

is there any "how to" for noobs with this wallet mess??? one that has at least the names right? iguana? agama? since yesterday im trying to move my funds to bittrex and only end up with error messages .... is iguana non functional? whats up with this agama thing and the java errors? I'm not really much of a technical guy and im constantly stuck with this here .... ty for any help

7enuke

member

Activity: 107

Merit: 10

REDDCoin - Great return

how i can exchange BTCD to KMD ?

7enuke

member

Activity: 107

Merit: 10

REDDCoin - Great return

Agama wallet Win 7 x64 error

[Window Title]
Error

[Main Instruction]
A JavaScript error occurred in the main process
[Content]
Uncaught Exception:
TypeError: shepherd.saveLocalAppConf is not a function
   at Function.shepherd.loadLocalConfig (C:\Program Files\AgamaApp\resources\app\routes\shepherd.js:125:14)
   at Object. (C:\Program Files\AgamaApp\resources\app\routes\shepherd.js:131:31)
   at Object. (C:\Program Files\AgamaApp\resources\app\routes\shepherd.js:1081:3)
   at Module._compile (module.js:571:32)
   at Object.Module._extensions..js (module.js:580:10)
   at Module.load (module.js:488:32)
   at tryModuleLoad (module.js:447:12)
   at Function.Module._load (module.js:439:3)
   at Module.require (module.js:498:17)
   at require (internal/module.js:20:19)
   at Object. (C:\Program Files\AgamaApp\resources\app\main.js:36:16)
   at Object. (C:\Program Files\AgamaApp\resources\app\main.js:402:3)
   at Module._compile (module.js:571:32)
   at Object.Module._extensions..js (module.js:580:10)
   at Module.load (module.js:488:32)
   at tryModuleLoad (module.js:447:12)

[OК]

jl777

legendary

Activity: 1176

Merit: 1134

Quote from: komodomining on March 30, 2017, 04:52:33 AM

Quote from: jl777 on March 25, 2017, 07:30:34 PM

Quote from: komodomining on March 25, 2017, 07:25:18 PM

Quote from: komodomining on March 25, 2017, 04:44:08 PM

Quote from: jl777 on March 25, 2017, 10:46:18 AM

Quote from: komodomining on March 25, 2017, 10:31:36 AM

Quote from: Kryptowerk on March 25, 2017, 10:27:12 AM

Quote from: komodomining on March 25, 2017, 06:42:00 AM

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

hi jl777 due an initial error in configuration, some rewards were sent to a our z_addr
Using z_gettotalbalance we see this reward in private and non in transparent.

if i try to use z_sendmay from z_add to t_add i receive this error :
Payment operation failed opid-56af3a46-f0ee-4394-92ff-b4240b8036a5 -1, runtime error: anchor is null

any workaround?

PM me a typical txid that funded the z-output

mrnakayouknowwho

newbie

Activity: 26

Merit: 0

Silly that we can't request another swap payout when we have once pending already.

Also would be great if you could process the swap payouts once per day / every other day.

komodomining

full member

Activity: 156

Merit: 100

Quote from: jl777 on March 25, 2017, 07:30:34 PM

Quote from: komodomining on March 25, 2017, 07:25:18 PM

Quote from: komodomining on March 25, 2017, 04:44:08 PM

Quote from: jl777 on March 25, 2017, 10:46:18 AM

Quote from: komodomining on March 25, 2017, 10:31:36 AM

Quote from: Kryptowerk on March 25, 2017, 10:27:12 AM

Quote from: komodomining on March 25, 2017, 06:42:00 AM

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

hi jl777 due an initial error in configuration, some rewards were sent to a our z_addr
Using z_gettotalbalance we see this reward in private and non in transparent.

if i try to use z_sendmay from z_add to t_add i receive this error :
Payment operation failed opid-56af3a46-f0ee-4394-92ff-b4240b8036a5 -1, runtime error: anchor is null

any workaround?

komodomining

full member

Activity: 156

Merit: 100

Quote from: 95do on March 29, 2017, 12:23:19 PM

i mined on http://komodominingpool.com/ and it says they paid but payment never came in wallet and now their site is down

Hi, yesterday we have made some configuration and for this reason site went down for 2/3 hours.
Now it's ok, today there may be minor interruptions, but just for a few minutes
Thank you

gee zee

newbie

Activity: 46

Merit: 0

Hi there, new Agama wallet doesn't work. I think it will be fixed soon. but my main issue is kmd explorer doesn't show my Balance. Sad

mankeen

sr. member

Activity: 644

Merit: 292

Hi
I have problem with my wallet Iguana
I can't send kmd to exchanges
how fix it?

hansen.ng

sr. member

Activity: 632

Merit: 250

Quote from: TakeItEasy on March 30, 2017, 01:43:11 AM

The latest official wallet version is AgamaApp-0.1.6.1e-beta ? Am i right ? Or can i still use Iguana ? And what Iguana latest version is ?
Thank you.
Awesome project. Haters move to other thread, price will not go down any more )

Yes, that's the latest wallet version. if it's not working, try the previous version.

TakeItEasy

sr. member

Activity: 1622

Merit: 270

Undeads.com - P2E Runner Game

Quote from: ptytrader on March 30, 2017, 01:53:14 AM

The new wallet is called Agama. The name was changed due to some changes in the wallet. There's a story about it on slack Cheesy

I have been testing it for the past few days and it seems more stable. I can't wait until our DEX is active.

Ok. Thank you. Will try it.

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