NEM Wallet Beta 2.4.4 - Bug bounty paid in XEM

[deleted_user_1]

Hello @Quantum_Mechanics and community.

First of all, congratulations for the huge effort that you’re doing to maintain and grow NanoWallet.

As an improvement for future releases, I would like that the post includes the checksum to ensure the validity of the file. What do you think?

I leave here the sha256sum for future readers.

08d963a7a537dbb32ff5278c1958f56f1c2baa20b7a29e5c5e4e4f7e70b47ee5 NanoWallet-1.3.4 -- Apostille TX f9a506e3abfa225d60b4447017279a6af7561428e0f53839fb3bea92fe8c129d -- Date 2017-04-20.zip

Best,

[deleted_user_1]

Even NanoWallet could be distributed via GitHub releases instead of Dropbox link, could it?

[Quantum_Mechanics]

Hi, checksum is now added to the op .

Even NanoWallet could be distributed via GitHub releases instead of Dropbox link, could it?

Yeah I think it could, will look into it for the next release

[Jkon]

I don’t know if this is considered as a bug but i think it is a issue that could be approved. First time i created a wallet and logged into it the node was automatically chosen and active. The second time i logged in the node was not chosen automatically. And for a new person using the wallet it gave me almost a heart attack to not see my account balance. Could the wallet have maybe a text in dashboard to make it very clear when node is not selected? The text: nothing to show is pretty alerting :D.
Maybe something like: nothing to show here, select a node
Even adding a text that tells that the nodes are safe to connect would probably decrease problems with new account owners.

Another thing I noticed:
Updating the market information doesn’t seem to update the USD balance.

-J

ND6NJZ-AZLZS4-PWYMUH-4ERJNU-YIYZWO-FFKH2X-SLXK

[Quantum_Mechanics]

Hi, the default node can be down sometimes probably because it gets a lot of traffic.

Changing the node manually from the navbar update the node in your local storage too so it should reconnect to the last node you have picked.

I am working on fetching the closest supernode from user location or use default if it can’t.

Updating the market information doesn’t seem to update the USD balance.

It can take a few minutes for the APIs of market providers to be updated

[Quantum_Mechanics]

Version 1.3.12

• Improve start / stop delegated harvesting design
• Fix market data percentage change
• Allow only one cosignatory removal per multisig edit
• Prevent multisig edit to make a 0 of m (= m of m)
• Module to sign multisig transactions if not pushed into your unconfirmed transactions
• Fetch the closest node from user location (https://www.w3schools.com/html/html5_geolocation.asp)
• Minor fixes and improvements

[mizunashi]

@Quantum_Mechanics
Is not git tag attached? I feel that there was a topic somewhere.

[Quantum_Mechanics]

I wanted to but Github release does not allow spaces in file names so the audit via Apostille would fail…

[jabo38]

Just released the bounty was still high so lowered it from 5000 to 500.

[GodTanu]

I have reported a couple of times but never got a reward until now.
I have also reported several times in past repositories.
Really have rewards?

[GodTanu]

The download page is still ver1.3.4.
Please update to the current latest.

https://nem.io/install.html

[Saul]

Ok will do.

[mizunashi]

I have never gotten either.
Although I have personally received chips.

NCVGXT-CV7YYG-CUTOWR-SEALEV-HVTDFR-J54BQY-DKTI

[Quantum_Mechanics]

Hi,

@GodTanu, @mizunashi

Sorry, we are pretty busy lately. I will take a moment to check and forward to Jeff for payment.

[jabo38]

Hi guys. We haven’t paid bounties in the lonnnnngest time. I apologize. I need to work with Mixmaster to arrange a date, but it always seems like we are busy.

[mizunashi]

About Levy setting at mosaic issue

When trying to collect 1 XEM by percentile method at 1 mosaic transmission, I found a problem.

Levy setting in 1 mosaic is collected by XEM as a percentile.
At that time, setting Levy fee to 99,999,999 will be displayed as expected.

However, if Levy fee is set to 100,000,000 all patterns become zero as shown below.

Is it just a display problem?
Or is this Levy fee specification outside the setting range?

By the way, even with Absolute the display breaks at 100,000,000

As a similar problem, there is setting of the initial issue volume.
There is no problem until the initial issue volume is 999,999,999

When it becomes 1,000,000,000 , the item at the time of sending the whole amount becomes zero as shown below.

Similarly, I do not know what is wrong.

At first, I thought it was a problem of numerical format that display could not be done well.
However, if zero is displayed, mosaic can not be issued.

I think that collection of 1 XEM around one mosaic, even if it exists, does not matter, is this a specification?

[fher98]

Hello everyone, How do I use nano wallet with testnet?

[logart]

I found a bug that makes the error “Can’t fetch market data” https://github.com/NemProject/NanoWallet/issues/67?_pjax=%23js-repo-pjax-container

No market Data in nano wallet

i think found the problem Saul poloniex thinks i am a bot. It will force me to do captcha every 2 minutes when i'm logged in their website. I think you guys need to take the data from somewhere else, because poloniex is too strict. Yeah i downloaded the last version, i still have the same problem and is because of captcha, pretty sure.

Where is my bounty :P? Nobody has answered me about this bug i found.

[tongokongo]

Sign-up. Than just use the testnet as a network.

[fher98]

Thank you!