Drai



Offline



Activity: 568

Merit: 270









Sr. MemberActivity: 568Merit: 270

Re: [ANN][KMD][dPoW] Komodo - Zcash Zero Knowledge Privacy Secured by Bitcoin June 16, 2017, 07:26:00 AM #9930 Quote from: jl777 on June 14, 2017, 05:58:37 AM



If you notice the coin holdings, SuperNET now has over 1% of two top 10 coins and reasonably liquid holdings in excess of $30 million USD equivalent.



We had been operating on a tight budget due to limited funds, but now that our funds have multiplied, it is time to expand the budget. Also, the tech is now reaching the initial release stage for JUMBLR and also DEX, along with migration from NXT assets into their own assetchains.



I would like to announce an active recruitment for a fulltime team dedicated to each of the SuperNET core assets: JUMBLR, DEX, PANGEA, BOTS, CRYPTO. Initially we will focus on the first two or three that are closest to product release.



Approximate budget for each asset is $1 million USD worth of crypto. Which should be enough to pay decent salary and marketing costs for initial launch. After launch, the goal is to get each asset self-sustaining and to generate a steady stream of revenues for its holders.



If you are interested in being the CEO or lead dev or marketing for any of these projects, please contact @pondsea who will be coordinating the recruitment process.



At the end of the initial product release cycles, my hope is that SuperNET will start trading as a high tech growth company that happens to have a large book value in liquid assets, instead of as a closed end investment fund at a discount to NAV.



Also, this is just the halfway point (approx), we are in a marathon and still have a ways to go before there is a fully decentralized automated money making machine.



It is interesting to see a lot of my ideas from years ago being duplicated in different contexts and raising incredible amounts of funds, based on whitepapers and not any working system. This tech is not easy by any means and has taken years to get to where it is and likely a few more before it can be considered in maintenance mode. I am glad that we are finally moving away from the pure bitcoin clones and now there is a very large spectrum of crypto projects and all are able to obtain the required financing.



The landscape has indeed changed and we are on course for a truly decentralized economy that operates in parallel to the fiat economies.



Exciting times ahead.

In the past SuperNET had to overcome many obstacles just to survive the bear market. Now the bull market has helped us achieve: http://old.supernet.org/nav.php If you notice the coin holdings, SuperNET now has over 1% of two top 10 coins and reasonably liquid holdings in excess of $30 million USD equivalent.We had been operating on a tight budget due to limited funds, but now that our funds have multiplied, it is time to expand the budget. Also, the tech is now reaching the initial release stage for JUMBLR and also DEX, along with migration from NXT assets into their own assetchains.I would like to announce an active recruitment for a fulltime team dedicated to each of the SuperNET core assets: JUMBLR, DEX, PANGEA, BOTS, CRYPTO. Initially we will focus on the first two or three that are closest to product release.Approximate budget for each asset is $1 million USD worth of crypto. Which should be enough to pay decent salary and marketing costs for initial launch. After launch, the goal is to get each asset self-sustaining and to generate a steady stream of revenues for its holders.If you are interested in being the CEO or lead dev or marketing for any of these projects, please contact @pondsea who will be coordinating the recruitment process.At the end of the initial product release cycles, my hope is that SuperNET will start trading as a high tech growth company that happens to have a large book value in liquid assets, instead of as a closed end investment fund at a discount to NAV.Also, this is just the halfway point (approx), we are in a marathon and still have a ways to go before there is a fully decentralized automated money making machine.It is interesting to see a lot of my ideas from years ago being duplicated in different contexts and raising incredible amounts of funds, based on whitepapers and not any working system. This tech is not easy by any means and has taken years to get to where it is and likely a few more before it can be considered in maintenance mode. I am glad that we are finally moving away from the pure bitcoin clones and now there is a very large spectrum of crypto projects and all are able to obtain the required financing.The landscape has indeed changed and we are on course for a truly decentralized economy that operates in parallel to the fiat economies.Exciting times ahead.

Do you think that with all the available liquidity will you be able to refund 630 kmd lost because of the interests bugs that komodo team wasn't aware of its presence in komodo gui wallet?



I mean, why have I to pay for it?



Quote from: Drai on June 13, 2017, 05:25:02 PM Quote from: ptytrader on June 11, 2017, 04:49:49 AM Quote from: Drai on June 10, 2017, 07:35:22 PM Quote from: ptytrader on June 10, 2017, 04:54:43 PM ... I suggest to anyone that hasn't moved their coins to a wallet under your control, that you do so soon.

Quote from: Drai on June 09, 2017, 12:41:10 PM

I would like to know who mined this block

http://kmd.explorer.supernet.org/block/000000464e48418bb3423c21c29eb1f31bf847e8ea9e39b59e54f64d5e773340



...I have to ask refund for 630 kmd for a transaction sent with bugged komodo swing wallet

I would like to know who mined this block...I have to ask refund for 630 kmd for a transaction sent with bugged komodo swing wallet

I asked publicly and privately to komodoPlatform before to send a transaction, for more then a month. Tried with Agama and resuted in strange behaviour and led me to wait until has been suggested to use a bugged version.



Can you please help me to find out who mined that block, so that maybe, the lost komodos will be in the address in my control when then snapshot will be took, please?

... I sent it when that wallet was considered a good solution.I asked publicly and privately to komodoPlatform before to send a transaction, for more then a month. Tried with Agama and resuted in strange behaviour and led me to wait until has been suggested to use a bugged version.Can you please help me to find out who mined that block, so that maybe, the lost komodos will be in the address in my control when then snapshot will be took, please?

I don't see a 630 KMD transaction in the blockhash you mentioned. Even though the gui wallets have had bugs, you should still have access to your funds if you saved your privatekeys or seed as with all wallets. Please open a new ticket and I will try to help you get an answer:

I don't see a 630 KMD transaction in the blockhash you mentioned. Even though the gui wallets have had bugs, you should still have access to your funds if you saved your privatekeys or seed as with all wallets. Please open a new ticket and I will try to help you get an answer: http://support.supernet.org/support/tickets/new

Since the interrogation of notary nodes resulted negative, how to determine which mining pool mined that block?



Quote from: Drai date=1497260744

wasn't aikapool. there are few blocks on its site stats;

Wasn't luckpool. These its blocks

Code: 359505 Mon Jun 12 2017 04:07:34 GMT-0400 (EDT) 3 1208 2.97472161 KMD

359262 Sun Jun 11 2017 23:42:59 GMT-0400 (EDT) 6 18307 2.95417896 KMD

357055 Sat Jun 10 2017 09:59:15 GMT-0400 (EDT) 3 201 2.97620227 KMD

357039 Sat Jun 10 2017 09:45:15 GMT-0400 (EDT) 3 347 2.970451 KMD

357014 Sat Jun 10 2017 09:22:15 GMT-0400 (EDT) 4 6769 2.96848418 KMD

356546 Sat Jun 10 2017 01:52:12 GMT-0400 (EDT) 4 6506 2.970451 KMD

356252 Fri Jun 09 2017 20:44:10 GMT-0400 (EDT) 5 1617 2.9619708 KMD

356171 Fri Jun 09 2017 19:25:09 GMT-0400 (EDT) 6 14612 2.9601739 KMD

355048 Thu Jun 08 2017 23:38:02 GMT-0400 (EDT) 8 5612 2.98577232 KMD

354731 Thu Jun 08 2017 18:34:00 GMT-0400 (EDT) 6 1658 2.96020737 KMD

354669 Thu Jun 08 2017 17:32:59 GMT-0400 (EDT) 7 3329 2.96957976 KMD

354472 Thu Jun 08 2017 14:00:58 GMT-0400 (EDT) 5 1826 2.96839456 KMD

354373 Thu Jun 08 2017 12:24:58 GMT-0400 (EDT) 7 2263 2.99569331 KMD

354225 Thu Jun 08 2017 09:55:57 GMT-0400 (EDT) 5 2676 2.96166028 KMD

354074 Thu Jun 08 2017 07:39:56 GMT-0400 (EDT) 6 439 2.96386408 KMD

354043 Thu Jun 08 2017 07:12:56 GMT-0400 (EDT) 5 31 2.970451 KMD

354040 Thu Jun 08 2017 07:09:56 GMT-0400 (EDT) 5 263 2.98711791 KMD

354023 Thu Jun 08 2017 06:56:56 GMT-0400 (EDT) 5 2968 2.96292958 KMD

353872 Thu Jun 08 2017 04:10:55 GMT-0400 (EDT) 5 690 2.97776635 KMD

353830 Thu Jun 08 2017 03:10:55 GMT-0400 (EDT) 5 4661 2.96313564 KMD

353703 Thu Jun 08 2017 01:07:54 GMT-0400 (EDT) 6 644 2.97171889 KMD

353687 Thu Jun 08 2017 00:54:54 GMT-0400 (EDT) 6 2769 2.9678976 KMD

353640 Thu Jun 08 2017 00:14:54 GMT-0400 (EDT) 8 6904 2.97978208 KMD

353429 Wed Jun 07 2017 20:31:52 GMT-0400 (EDT) 6 3352 2.95675 KMD

353286 Wed Jun 07 2017 18:19:52 GMT-0400 (EDT) 7 1515 2.97258543 KMD

353235 Wed Jun 07 2017 17:32:52 GMT-0400 (EDT) 7 1089 2.97355211 KMD

353195 Wed Jun 07 2017 16:50:52 GMT-0400 (EDT) 7 2685 2.98126659 KMD

353111 Wed Jun 07 2017 15:30:51 GMT-0400 (EDT) 4 2845 2.9522752 KMD

353005 Wed Jun 07 2017 13:44:50 GMT-0400 (EDT) 5 1858 2.98362285 KMD

352947 Wed Jun 07 2017 12:46:50 GMT-0400 (EDT) 5 1447 2.97368743 KMD

352905 Wed Jun 07 2017 12:08:50 GMT-0400 (EDT) 5 6795 2.96846293 KMD

352621 Wed Jun 07 2017 06:53:49 GMT-0400 (EDT) 4 3567 2.96738102 KMD

352450 Wed Jun 07 2017 04:11:48 GMT-0400 (EDT) 6 2346 2.96979221 KMD

352370 Wed Jun 07 2017 03:00:48 GMT-0400 (EDT) 7 4236 2.97875318 KMD

352195 Tue Jun 06 2017 23:51:47 GMT-0400 (EDT) 5 267 2.96866234 KMD

352186 Tue Jun 06 2017 23:43:47 GMT-0400 (EDT) 5 2456 2.97308824 KMD

352063 Tue Jun 06 2017 21:51:46 GMT-0400 (EDT) 5 2841 2.97326523 KMD

352003 Tue Jun 06 2017 21:02:46 GMT-0400 (EDT) 6 1030 3.00084795 KMD

351968 Tue Jun 06 2017 20:38:46 GMT-0400 (EDT) 6 2987 2.9698622 KMD

351879 Tue Jun 06 2017 18:24:46 GMT-0400 (EDT) 6 516 2.9703683 KMD

351862 Tue Jun 06 2017 18:06:45 GMT-0400 (EDT) 7 2376 2.97117517 KMD

351790 Tue Jun 06 2017 16:53:30 GMT-0400 (EDT) 6 4469 2.96742492 KMD

351655 Tue Jun 06 2017 14:48:30 GMT-0400 (EDT) 6 811 2.96929346 KMD

351630 Tue Jun 06 2017 14:21:30 GMT-0400 (EDT) 6 2909 2.96997955 KMD

351539 Tue Jun 06 2017 12:55:29 GMT-0400 (EDT) 5 5773 2.96995672 KMD

351308 Tue Jun 06 2017 09:09:28 GMT-0400 (EDT) 4 2657 2.97017798 KMD

351192 Tue Jun 06 2017 07:16:28 GMT-0400 (EDT) 5 2730 2.97026347 KMD

351097 Tue Jun 06 2017 05:41:28 GMT-0400 (EDT) 5 7072 2.97104937 KMD

350879 Tue Jun 06 2017 01:24:26 GMT-0400 (EDT) 4 3709 2.96994999 KMD

Payment Tue Jun 06 2017 01:03:26 GMT-0400 (EDT) 59 0 2.95381264 KMD

350738 Mon Jun 05 2017 23:13:57 GMT-0400 (EDT) 4 7441 2.96999999 KMD

350444 Mon Jun 05 2017 18:21:55 GMT-0400 (EDT) 5 6062 3.11741394 KMD

350171 Mon Jun 05 2017 13:55:54 GMT-0400 (EDT) 3 1054 2.8425561 KMD

350155 Mon Jun 05 2017 13:41:55 GMT-0400 (EDT) 5 11421 3.00086913 KMD

349768 Mon Jun 05 2017 05:30:08 GMT-0400 (EDT) 5 3320 2.97021002 KMD

349644 Mon Jun 05 2017 03:36:08 GMT-0400 (EDT) 4 3673 3.07129157 KMD

349398 Sun Jun 04 2017 23:27:07 GMT-0400 (EDT) 3 5127 2.847642 KMD

349214 Sun Jun 04 2017 20:26:06 GMT-0400 (EDT) 4 5509 3.02048889 KMD

349097 Sun Jun 04 2017 18:14:05 GMT-0400 (EDT) 3 5152 2.90275768 KMD

349043 Sun Jun 04 2017 17:18:05 GMT-0400 (EDT) 4 38 2.99435092 KMD

349042 Sun Jun 04 2017 17:17:05 GMT-0400 (EDT) 3 1206 2.91564413 KMD

349028 Sun Jun 04 2017 17:04:05 GMT-0400 (EDT) 3 850 2.92323731 KMD

349017 Sun Jun 04 2017 16:55:05 GMT-0400 (EDT) 4 1898 3.03323149 KMD

348997 Sun Jun 04 2017 16:38:05 GMT-0400 (EDT) 3 3652 2.99589561 KMD

348970 Sun Jun 04 2017 16:16:05 GMT-0400 (EDT) 2 722 2.86044533 KMD

348965 Sun Jun 04 2017 16:09:05 GMT-0400 (EDT) 4 5816 3.06645504 KMD

348847 Sun Jun 04 2017 14:27:04 GMT-0400 (EDT) 4 7311 2.9205274 KMD

348796 Sun Jun 04 2017 13:28:04 GMT-0400 (EDT) 4 5489 2.91810909 KMD

348717 Sun Jun 04 2017 13:06:04 GMT-0400 (EDT) 5 3472 3.03772083 KMD

348752 Sun Jun 04 2017 13:05:04 GMT-0400 (EDT) 4 3727 2.89700263 KMD

348680 Sun Jun 04 2017 11:12:21 GMT-0400 (EDT) 4 2211 2.90670189 KMD

348661 Sun Jun 04 2017 10:53:21 GMT-0400 (EDT) 5 7345 3.06159233 KMD

348605 Sun Jun 04 2017 10:06:21 GMT-0400 (EDT) 3 55 2.92755576 KMD

348604 Sun Jun 04 2017 10:05:21 GMT-0400 (EDT) 4 3639 3.06877249 KMD

348555 Sun Jun 04 2017 09:18:21 GMT-0400 (EDT) 3 12262 2.93975504 KMD

348409 Sun Jun 04 2017 06:55:20 GMT-0400 (EDT) 4 378 2.96723849 KMD

348405 Sun Jun 04 2017 06:52:20 GMT-0400 (EDT) 3 60 2.92021999 KMD

348404 Sun Jun 04 2017 06:51:20 GMT-0400 (EDT) 4 1927 2.90895818 KMD

348385 Sun Jun 04 2017 06:36:20 GMT-0400 (EDT) 4 366 2.92257975 KMD

348379 Sun Jun 04 2017 06:27:20 GMT-0400 (EDT) 6 5017 3.15453688 KMD

348325 Sun Jun 04 2017 05:22:20 GMT-0400 (EDT) 4 16197 2.90348028 KMD

348183 Sun Jun 04 2017 03:21:19 GMT-0400 (EDT) 4 620 2.91340492 KMD

348176 Sun Jun 04 2017 03:16:19 GMT-0400 (EDT) 5 3095 3.03498252 KMD

348158 Sun Jun 04 2017 02:55:19 GMT-0400 (EDT) 4 3854 2.90417692 KMD

348130 Sun Jun 04 2017 02:19:19 GMT-0400 (EDT) 4 3176 2.90911849 KMD

348096 Sun Jun 04 2017 01:48:19 GMT-0400 (EDT) 6 522 3.12234332 KMD

348088 Sun Jun 04 2017 01:42:19 GMT-0400 (EDT) 4 9452 2.90241082 KMDpiv

348007 Sun Jun 04 2017 00:13:18 GMT-0400 (EDT) 4 349 2.93402468 KMD

348005 Sun Jun 04 2017 00:12:18 GMT-0400 (EDT) 4 1986 2.93070382 KMD

347988 Sun Jun 04 2017 00:01:18 GMT-0400 (EDT) 5 6787 3.06160274 KMD

347916 Sat Jun 03 2017 22:56:18 GMT-0400 (EDT) 3 7184 2.94302675 KMD

347834 Sat Jun 03 2017 21:15:17 GMT-0400 (EDT) 3 17 2.96994999 KMD

347833 Sat Jun 03 2017 21:14:17 GMT-0400 (EDT) 3 2445 2.93902899 KMD

347794 Sat Jun 03 2017 20:38:17 GMT-0400 (EDT) 3 2559 2.93614153 KMD

347757 Sat Jun 03 2017 19:54:17 GMT-0400 (EDT) 4 612 3.0663815 KMD

347756 Sat Jun 03 2017 19:51:17 GMT-0400 (EDT) 4 1411 2.93611455 KMD

347743 Sat Jun 03 2017 19:40:17 GMT-0400 (EDT) 4 20903 2.94039616 KMD

347496 Sat Jun 03 2017 15:27:40 GMT-0400 (EDT) 5 12310 3.02473712 KMD

347318 Sat Jun 03 2017 11:47:48 GMT-0400 (EDT) 4 11985 2.94104168 KMD

347185 Sat Jun 03 2017 09:41:47 GMT-0400 (EDT) 6 1166 3.04467484 KMD





wasn't aikapool. there are few blocks on its site stats;Wasn't luckpool. These its blocks



KomodoPool.com

zpool

AlvBlock Pool

Komodo Mining Pool

MiningSpeed Pool

suprnova.cc

MinerCity

Spiry Corp. Pools



Do you see any chance I can get rid of it?

Since the interrogation of notary nodes resulted negative, how to determine which mining pool mined that block?Which among:KomodoPool.comzpoolAlvBlock PoolKomodo Mining PoolMiningSpeed Poolsuprnova.ccMinerCitySpiry Corp. PoolsDo you see any chance I can get rid of it? Do you think that with all the available liquidity will you be able to refund 630 kmd lost because of the interests bugs that komodo team wasn't aware of its presence in komodo gui wallet?I mean, why have I to pay for it?