@chem96: Try to run it with admin rights. In native mode it can take up to 9 hours on windows, but just for the whole blockchain. After it will be faster. You also could go to advanced settings and choose LITE mode that connects to SPV and you don't need to wait, because it will not download the blockchain.

I have some questions:

1) Suppose I owned KMD while JUMBLR snapshot happened. If today I move KMD from one address to another in native mode, can it happen that some addresses disappear? I saw that behaviour in Swing wallet, that after transfers, 1 or 2 new addresses are generated and filled with KMD and one gets "deleted" from the list of addresses after transaction. So if I not export the priv keys of all addresses BEFORE the transaction I can loose access of other assets like JUMBLR?

Or do I stay with all ever generated addresses in Agama forever even after n transactions and with 0 balance on some addresses and that was just a bug in Swing wallet?

2) Will the GUI for the MONAIZE dICO have "import Agama seed" AND "import priv key" funcionality?

3) Does the last Agama release have Seed (basilisk or similar) funcionality?

For sure. Once the new GUIs are out and the dICO happen, we will see a rise.

@xmofuffo: they are working on a new release of Agama that is more stable and resolves the known issues. As I understood it is just a matter of some days or a few weeks from now.

The website looks great and the announcements were solid.

How is it possible to do transactions from one tangle to another? Does it crete links between the tangles or are the transactions from one wallet going to different not connected tangles depending on the transaction? (therefore new adresses with each new transaction?)

I'm really excited about the development and news on Komodo and SuperNET. There is still a long road ahead. Thanks to all developers.

After I clicked to "attach", adress was attached. Then (after I saw, "adress attached") I made an transfer from another wallet to my newly created adress (that I attached). But I did that transfer before the attachment (bundle) was confirmed. The transfer is already confirmed, but I cannot see it on the wallet.

Should I rebroadcast the unconfirmed (for 2 hours) bundle?

Questions or ideas for BarterDEX GUI interface capabilities:

As different users may use different wallets/GUIs a user could choose inside the BarterDEX GUI for each coin what wallet he already uses on his local machine. As I understand correctly just native mode wallets will be supported in the beginning.

If so, also AGAMA could be choosen for each coin, if it's running in native mode. That could integrate AGAMA and BarterDEX even more and it could be merged one day (within AGAMA you could than specify if you want AGAMA to create your wallet or use a existing wallet that is managed by a third parties GUI).

Basilisk mode: A user could choose trusted servers that save his adress and run a trade or alternatively the adress that starts the trade could be sent to the network like an transaction/smart contract, and once online (the trade contract) and confirmed by the decentralized network, it could be executed independently if the traders are online or not and the coins already can be transfered to the trader adress(es). When he is back online, his wallet gets updated as it connects to the server or decentralized network that stores his smart contract on the blockchain.

Sure, I was just confused, because of that reliability post.
Is that just abaut the 5% interest that could be lost in basilisk?


And also that quote "with barterDEX, if you get a connection error, you will likely lose the funds for your trade".
I did not understand that. Why would one loose their funds if a connection problem occures? Right before the trade process starts the traders adress could be send to the network and only if the network send back "ok" to the trader than the trade process could be started and even in the event that the trader has any kind of connection problem before the trading process finishes, it could be done in the network and after he is back online, he could get his coins on his adresses.

Is it safe to transfer KMD from agama wallet in basilisk mode right now or can funds get lost when there is no network connection to extern nodes in the time of transfer?

questions:

Let's say I bought some IOTA in bitfinex. Now I create an own wallet and transfer my IOTA to the wallet to not be dependent on future events that may occur on the centralized exchange.

Well, at IOTA I also choose a NODE-server in light mode. If I choose the server bitfinex offers (or any other), is it not the same as to store it directly on an centralized exchange?

What happens, if the server goes down for example or hacked? Aren't my funds lost as well?
Or are my funds copied to every other IOTA tangles?

If it's just on one tangle and the tangle dies due to hacks or deletion, than the funds are lost?

Did I miss the announcement of a date of the JUMBLR snapshot? Or is it after completion of ICO distribution and swaps, in the beginning of 2018?

I just want to be sure, to be able to prepare my wallets.

Ok, as the snapshot will be done for all the existing T adresses, I guess it doesn't matter, if I use Agama in basilisk mode or native to see and get the JUMBLR. Is that correct?

Yes that makes sense. I have access to the private keys in the swing-wallet. But do I need to import them into another wallet or will the komodo-swing-wallet show me the JUMBLR balance and will it let me spend it just out of it?

If yes, ok. If not, the agama in basilisk doesn't show the priv key, or does it? I just need the seed and have my one and only adress to send and receive KMD. So do I get JUMBLR for that kind of basilisk adresses? (or just after "converting" it to a native adress with priv key?)

Great progress in the Komodo Platform. For those who believe in the future of cryptocurrencies, that is really awesome and I think that Komodo and Supernet will have a big role in future developments.

I have the same question as the person posted before: Will KMD in the komodo-swing-wallet automatically participate on the Jumblr snapshot or is it needed to transfer KMD to a AGAMA wallet? (if yes, is the mode important for the snapshot? basilisk/native?)

If for whatever reason the komodo swing wallet now or in future won't work anymore, is the backed-up wallet.dat (at a time and blockheight when the app still worked) save?

With save I mean, are the funds (KMD) accessible by importing the wallet.dat into other applications (Agama etc.)?

@KomodoPlatform: Thank You. I have registered at slack and entered in the channel #komodo, I hope that was right, as I did not see any #support channel.

I do see my balance now, so I think the import process has somehow worked. But my komodo-swing-wallet does not get beyond blockchain height 21.06.2017 18:20:23. Are there any known issues? I tested with two computers and got the same result. I also cannot send Komodo to another adress as my app is kind of freezing then (on both computers, win10, 64bit, 16gb ram). The network is working, 8 connections showing up.

Is it enough to just backup the wallet.dat, for a new release of the komodo-swing-wallet, to be able to make transactions? The backup can be done manually just by copying it in the windows dir? Or do I need to do it within the komodo-swing-wallet? If yes, that doesn't work either. I get another error message.

That's the error message I get while importing the seed in komodo-swing-wallet:


The blockchain is fully downloaded until today (24.06.2017) and I have no network issues.
Any idea?