Print

• Show the most recent posts.

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[nxtforum-a]

What I did: opened a private window, imported my passphrase, waited for the generation of the addresses, logged out, closed the private window (VRC address started with b55).
Then, hit Ctrl+shift+R on the "normal" supernet wallet, logged in, hit Ctrl+shift+R again, re-logged in, and the VRC address is still the old one (it starts with bVX).

Yes, well, the problem is that a private browser session does not remember anything in the browser cache So that allows you to check the address generated by new servers, but not to remember it; for as long as the obsolete one is stored in your browser cache, that's the one you'll see in a regular browser session. Until you clean your browser cache, which should solve the problem by flushing the stuck obsolete address.

In fact no, that didn't solve anything: I cleared my firefox cache (several times until 0 bytes was displayed), I removed also my imported passphrase, but nothing did the trick.
I also noticed "SuperNet Version 2.0.5" is displayed, although I'm sure I'm using 2.0.6. Perhaps the file used to display this has not been updated? I overwrote the directory to upgrade from 2.0.5 to 2.0.6...

[Arkh]

@VanBreuk

Thanks for your answer !

I'm sorry I didn't kept updated about that, my bad. I'll use the new lite client & superBTC next time then, it's weird that the order book for those is empty though.

If it's too much of a hassle to run the old mgwBTC you might return me the BTC if it's possible, then I'll use the superBTC

[VanBreuk]

I overwrote the directory to upgrade from 2.0.5 to 2.0.6...

I'm not sure that is a safe way to update. Have you tried to unzip the release in its own folder and run?

Tosch110 may have a say about this, so I'm cross posting in the SN Lite release thread.

I'll use the new lite client & superBTC next time then, it's weird that the order book for those is empty though.

If it's too much of a hassle to run the old mgwBTC you might return me the BTC if it's possible, then I'll use the superBTC

Of course we're running the mgwBTC, and anyone who sent a deposit will receive the assets. And of course anyone who holds mgwBTC can swap them for superBTC. I just hope that the old MGW servers will cooperate a bit more and help to automate the coin migration process, because doing manual multisig transfers in Bitcoin can be a pain and very time intensive. And the faster we can move the coins to the new wallets, the better.

The superBTC orderbook is understandably empty because very few BTC have been deposited so far in the SuperNET MGW. The same thing happened last year when development servers phased out. But as old servers go offline, the activity will move over. It's also much easier to know that, for as long as BTC/NXT block times are not unusual, depositing or withdrawing can take half an hour.

Don't worry, you'll receive your deposit. Then you can either sell in the AE or withdraw it back to a deposit address in the new servers (see how to swap mgwBTC to superBTC). If you do the latter, just keep in mind that processing time for withdraws through old servers is quite unpredictable, but once you're using superBTC, you'll have a much better service.
 

[nxtforum-a]

I overwrote the directory to upgrade from 2.0.5 to 2.0.6...

I'm not sure that is a safe way to update. Have you tried to unzip the release in its own folder and run?

Tosch110 may have a say about this, so I'm cross posting in the SN Lite release thread.

I didn't find anything on "how to update" when 2.0.6 was released, and, as I wanted to keep my contacts and my preferences settings, I did this. Perhaps an "UPDATE" file could be joined in the ZIP, or a section "HOW TO UPDATE" could be added in the README file, don't you think?

[mystcoin]

I made my first superBTC deposit over 6 hours ago and it hasn't appeared in my account yet. My new deposit address is 1JCBpsHFkHsW3nCFa9PsNxcyARXrLpoEes

[mystcoin]

I made my first superBTC deposit over 6 hours ago and it hasn't appeared in my account yet. My new deposit address is 1JCBpsHFkHsW3nCFa9PsNxcyARXrLpoEes

The above address was obtained manually. I tried requesting it again and got no response for a long while. When I got a reponse again, it appeared differently than before; now I have a deposit address that begins with 3: 3CnUjSaxnVLz6xR7qFaDDhTZfadoEGUnt6. I just tried this one and the deposit went through quickly.

The new response also had an array of three addresses beginning with 1, one of which is the address I first tried. Apparently, that is not the right address but perhaps it is the address of one of the servers. I used a small amount for testing, so don't mind losing it.

[jl777]

I made my first superBTC deposit over 6 hours ago and it hasn't appeared in my account yet. My new deposit address is 1JCBpsHFkHsW3nCFa9PsNxcyARXrLpoEes

The above address was obtained manually. I tried requesting it again and got no response for a long while. When I got a reponse again, it appeared differently than before; now I have a deposit address that begins with 3: 3CnUjSaxnVLz6xR7qFaDDhTZfadoEGUnt6. I just tried this one and the deposit went through quickly.

The new response also had an array of three addresses beginning with 1, one of which is the address I first tried. Apparently, that is not the right address but perhaps it is the address of one of the servers. I used a small amount for testing, so don't mind losing it.

all deposit addresses for BTC MGW start with "3"
the address starting with "1" is probably an internal address used to create the multisig

[nxtforum-a]

I overwrote the directory to upgrade from 2.0.5 to 2.0.6...

I'm not sure that is a safe way to update. Have you tried to unzip the release in its own folder and run?

Tosch110 may have a say about this, so I'm cross posting in the SN Lite release thread.

I didn't find anything on "how to update" when 2.0.6 was released, and, as I wanted to keep my contacts and my preferences settings, I did this. Perhaps an "UPDATE" file could be joined in the ZIP, or a section "HOW TO UPDATE" could be added in the README file, don't you think?

I made some tests yesterday, and the only way I found to have the new addresses available is to change the path of the supernet.html file (ie until this problem, I used to load file:///home/xxxxx/.supernet/ui/supernet.html in firefox, and now I load file:///home/xxxxx/.supernet-2.0.6/ui/supernet.html). This way the "cache" is *really* lost.
Is there a "geeker" solution than the firefox preferences tab? I deleted the firefox profile/storage/file++++home(...) directory, but that wasn't enough...

[Tosch110]

I overwrote the directory to upgrade from 2.0.5 to 2.0.6...

I'm not sure that is a safe way to update. Have you tried to unzip the release in its own folder and run?

Tosch110 may have a say about this, so I'm cross posting in the SN Lite release thread.

I didn't find anything on "how to update" when 2.0.6 was released, and, as I wanted to keep my contacts and my preferences settings, I did this. Perhaps an "UPDATE" file could be joined in the ZIP, or a section "HOW TO UPDATE" could be added in the README file, don't you think?

I made some tests yesterday, and the only way I found to have the new addresses available is to change the path of the supernet.html file (ie until this problem, I used to load file:///home/xxxxx/.supernet/ui/supernet.html in firefox, and now I load file:///home/xxxxx/.supernet-2.0.6/ui/supernet.html). This way the "cache" is *really* lost.
Is there a "geeker" solution than the firefox preferences tab? I deleted the firefox profile/storage/file++++home(...) directory, but that wasn't enough...

It is good that you have found a way to get rid of the cached addresses to generate new ones. Actually, as when I am developing, I am using the new version therefore I had not looked much into the problem of old and cached msig addresses.

I will look if I can find a way to make this automatically on startup. Anyway, this edge case should not be around for long as people switch to new MGW server and superBTC

[VanBreuk]

I will look if I can find a way to make this automatically on startup. Anyway, this edge case should not be around for long as people switch to new MGW server and superBTC

Awesome, thanks. But please note that this issue with old deposit addresses lingering in cache may affect only BTCD, VRC and OPAL currently. BTC, LTC and DOGE deposit addresses are necessarily coming from the new servers, because the previous SuperNET Lite release (2.0.5) did not feature them yet.

And the old mgwBTC releases worked with the (only) deposit address in a different way, so whatever BTC address appears in the SN Lite 2.0.6 dashboard has to be correct.

So this may only affect users who installed SN Lite 2.0.5 or earlier, want to deposit VRC, BTCD or OPAL, and haven't cleaned their browser cache.

It will be great to prevent it in the next release anyways.

[VanBreuk]

And about the ongoing migration of mgwBTC > superBTC, there's an update in the procedure posted here.

- How do I move my mgwBTC (asset ID 17554243582654188572) to the new v2 superBTC (asset ID 12659653638116877017) ?

In order to prevent some edge cases in this one time old-servers-to-new migration, the swap of mgwBTC for superBTC will be processed manually. Keep in mind that as assets are swapped coins are moved from old wallets to the new, in order to keep system balances at all times, so the swaps might be subject to small delays. So, in order to swap your assets:

- Send them to the MGW Redeem Account, NXT-6YQW-HHCG-NATW-DCHJ3. Verification:

text:

Code: [Select]

Nxt Redeem Account for MGW Asset Swaps: NXT-6YQW-HHCG-NATW-DCHJ3 - VanBreuk 14-Sept-2015token:

Code: [Select]

5q6ooq3juuls2rn1os7t1bkpl924d3seqto1jpal9d8reu65cjfuse5oveencso3gek0njuhda46nimu9o7ehudmneid0lvp90sjpudr5ne0t1hjtr4km4lrfo2f7p49rcfroa6drt6saif5do37rjmj7mb4krnc
We'll send back the equivalent amount of superBTC.

if instead of swapping your mgwBTC over to superBTC you prefer to withdraw them to an external Bitcoin account, please add a message to the mgwBTC asset transfer and provide the destination BTC account in the message. No special syntax is needed for this message since this will be processed manually.

- Once you have your superBTC, you can see them displayed in the dashboard of the new SuperNET Lite 2.0.6.

If anyone has submitted a mgwBTC withdraw and the coins haven't been received (either in superBTC account or external BTC account) please contact me so we give your tx a manual push if required.

[Pilot]

I overwrote the directory to upgrade from 2.0.5 to 2.0.6...

I'm not sure that is a safe way to update. Have you tried to unzip the release in its own folder and run?

Tosch110 may have a say about this, so I'm cross posting in the SN Lite release thread.

I didn't find anything on "how to update" when 2.0.6 was released, and, as I wanted to keep my contacts and my preferences settings, I did this. Perhaps an "UPDATE" file could be joined in the ZIP, or a section "HOW TO UPDATE" could be added in the README file, don't you think?

I made some tests yesterday, and the only way I found to have the new addresses available is to change the path of the supernet.html file (ie until this problem, I used to load file:///home/xxxxx/.supernet/ui/supernet.html in firefox, and now I load file:///home/xxxxx/.supernet-2.0.6/ui/supernet.html). This way the "cache" is *really* lost.
Is there a "geeker" solution than the firefox preferences tab? I deleted the firefox profile/storage/file++++home(...) directory, but that wasn't enough...

It is good that you have found a way to get rid of the cached addresses to generate new ones. Actually, as when I am developing, I am using the new version therefore I had not looked much into the problem of old and cached msig addresses.

I will look if I can find a way to make this automatically on startup. Anyway, this edge case should not be around for long as people switch to new MGW server and superBTC

Are we talking "cache" or "localStorage"? There is a difference. Clearing cache does not clear local storage.

To clear local storage open the wallet site, then open the Chrome DevTools console (buy pressing F12 or from the menu More Tools -> Developer Tools) .

In the console type...

localStorage.clear()

Press enter. You will get an "undefined" returned but that is expected.

Refresh your browser.

BTW: This same thing can be done in IE and FireFox. I think F12 is pretty command way to open dev tools, although, I'm not sure if they are installed by default with FireFox. You may need to add the FireBug add-in first to be able to get to the javascript console.

[oakmaster]

Hello all,

We're starting this thread to provide User Support for Multigateway (MGW). You can post here questions and problems you find when using the service.

- Latest client release featuring the MGW service: SuperNET Lite 2.0.6

- Current active coins and list of MGW asset IDs:

SuperNET MGW Assets

• superBTC - 12659653638116877017
• superBTCD - 6918149200730574743
• superDOGE - 16344939950195952527
• superLTC - 125609428220063838
• superOPAL - 6775076774325697454
• superVRC - 9037144112883608562

production mgwBTC asset - 17554243582654188572
> The gateways will stay active for a few weeks, but migration to SuperNET MGW is recommended to improve performance.

old development assets
mgwBTC - 4551058913252105307
mgwBTCD - 11060861818140490423
mgwLTC - 2881764795164526882
> The gateways went offline long ago, but if anyone still holds development assets, contact me in order to transfer the coins from old development wallets to your new SuperNET deposit account.

For specific issues with the SuperNET Lite client, please ask Tosch110 in the latest release thread.

If you want to report an issue, please include your Nxt Account ID or MGW coin address, and if possible the transaction ID related to the problem.

For a general description of the service, visit http://multigateway.org

I just realized I have mgwbc and mgwdoge can I still switch these to the  superbc and superdoge thanks

[VanBreuk]

I just realized I have mgwbc and mgwdoge can I still switch these to the  superbc and superdoge thanks

You can send mgwDOGE to the redeem account (see above) and we'll send superDOGE back.

For mgwBC you may need to wait some time because Blackcoin is not yet active in MGW v2, but it might be in the future. Like with futurist earlier in this thread, we can also swap your mgwBC for NXT or MGW assets at current market rates. Send me a PM if you want to do this.

[Tosch110]

I overwrote the directory to upgrade from 2.0.5 to 2.0.6...

I'm not sure that is a safe way to update. Have you tried to unzip the release in its own folder and run?

Tosch110 may have a say about this, so I'm cross posting in the SN Lite release thread.

I didn't find anything on "how to update" when 2.0.6 was released, and, as I wanted to keep my contacts and my preferences settings, I did this. Perhaps an "UPDATE" file could be joined in the ZIP, or a section "HOW TO UPDATE" could be added in the README file, don't you think?

I made some tests yesterday, and the only way I found to have the new addresses available is to change the path of the supernet.html file (ie until this problem, I used to load file:///home/xxxxx/.supernet/ui/supernet.html in firefox, and now I load file:///home/xxxxx/.supernet-2.0.6/ui/supernet.html). This way the "cache" is *really* lost.
Is there a "geeker" solution than the firefox preferences tab? I deleted the firefox profile/storage/file++++home(...) directory, but that wasn't enough...

It is good that you have found a way to get rid of the cached addresses to generate new ones. Actually, as when I am developing, I am using the new version therefore I had not looked much into the problem of old and cached msig addresses.

I will look if I can find a way to make this automatically on startup. Anyway, this edge case should not be around for long as people switch to new MGW server and superBTC

Are we talking "cache" or "localStorage"? There is a difference. Clearing cache does not clear local storage.

To clear local storage open the wallet site, then open the DevTools console. In the console type...

localStorage.clear()

good catch. thanks for the hint!

[chevdor]

I think I am missing a piece of information.
As I understand, mgwbtc should no longer be used but Supernet instead.

I´ve got SuperNet-Lite-2.0.6-Beta
Is that correct?

From there, how do I convert my NXT to BTC as I used to do with mgwBTC?

[VanBreuk]

I think I am missing a piece of information.
As I understand, mgwbtc should no longer be used but Supernet instead.

I´ve got SuperNet-Lite-2.0.6-Beta
Is that correct?

From there, how do I convert my NXT to BTC as I used to do with mgwBTC?

Next Lite client releases should make this more clear and accessible. Right now, the dashboard in SN Lite 2.0.6 works like a multiwallet where users can receive and send any of the supported coins (to either Nxt or external coin addresses). If you want to use any of the Nxt AE market pairs (NXT <> superCOIN) you can go to the Advanced mode in the top menu. That will open a classic Nxt client using Jay framework.

[VanBreuk]

ANNOUNCEMENT: Operators of old mgwBTC servers will be definitively pulling the plug and bringing servers offline the next tuesday, September 22nd, at 22:00 UTC.

This means that any mgwBTC server withdrawals that haven't been requested AND processed by then will expire and will need to be processed manually afterwards.

This also means that, after old servers go offline, recovering deposits sent to the old mgwBTC deposit addresses will be of course possible, but quite laborious, so please from now on send any new BTC deposits using the deposit address from the SuperNET Lite client. 

Holders of mgwBTC (asset ID 17554243582654188572) can swap them for superBTC (asset ID 12659653638116877017) anytime, following these instructions. This manual asset swap procedure does not have a deadline.

[Pilot]

Of course, the good news now is that assests can be deleted by sending them to Genesis which is where I assume all the mgwXXX tokens are bound for eventually. (Well, in 1.6 that is).

[VanBreuk]

Of course, the good news now is that assests can be deleted by sending them to Genesis which is where I assume all the mgwXXX tokens are bound for eventually. (Well, in 1.6 that is).

Yes, I thought about this the other day when reading 1.6.0e release. So far, all the "burned" MGW assets (due to testing, manual operations, etc) were sent to genesis as well. But now it will be... well, much cleaner.