bertlebbert
Well-known member
Sorry... I'm referring to the whole wallet containing 2994 tDash, not particularly individual address
V12 Testing Thread
- Thread starter eduffield
- Start date
moli
Well-known member
Yes, I believe you. Your wallet can have many coins in many addresses, but if an IX tx is from an address that has more than 1000 DASH like in my post above, it's another story. You see what I mean?
bertlebbert
Well-known member
Yeah I figured that out, sorry for the confusion
moli
Well-known member
No problem. It's a confusing issue. Like Udjin explained, when a tx has a change that goes to another address, the network can't tell if it's a change or it's another tx to another person, so it counts the total into one. So like if one address/account has 1002 DASH in total, and we send 10 DASH via InstantX, the change will be 992, but the network still sees the IX transaction as 1002. What I don't understand is the rule "Can't InstantX more than 1000 DASH". I hope the devs can change it
.
Last edited by a moderator:
TaoOfSatoshi
Well-known member
I don't think it would be an issue if, on attempting to InstantX coins that will get stuck due to being over 1000 DASH, a pop-up appeared to say "The address used for this InstantX transaction contains more than 1000 DASH. Addresses need to be broken down into less than 1000 DASH for InstantX to be successful. Would you like to proceed, YES or NO."
Maybe the wallet could perform this task automatically, upon selecting YES?
bertlebbert
Well-known member
Or why not the wallet just does so automatically when required, no pop-up or question asked... I don't know why I would care that it comes from address containing over 1000 coins
moli
Well-known member
Probably it will be changed to something similar like Udjin said: https://dashtalk.org/threads/v12-testing-thread.5484/page-24#post-57730
But I think it would be best if the network didn'tt care how much is being sent via IX from what account... like what bertlebbert said ..
1. Can we change 1000 DASH to a higher value?
Sure it's just another spork which is set to 1000 now.
2. Why can't wallet split huge amounts on IX automatically?
Because we require at leas 6 confirmations and that means you'll have to wait ~6 x 2.5 minutes = ~15 minutes to send IX from new addresses which were created by that split. Not that instant
Possible solution is to modify algo:
- to check that none of outputs is greater than 1000 (or whatever spork value is) and not the total tx value (that doesn't solve the problem when change is greater than 1000 though)
- to check that IX have 2 outputs maximum (and give a warning if that's not the case) to allow normal users to pay as usual but to prevent multi IX in single tx at the same time (still can do 2 IX at the same time if you have exact amount but that's and extreme edge case so not a big deal)
Sure it's just another spork which is set to 1000 now.
2. Why can't wallet split huge amounts on IX automatically?
Because we require at leas 6 confirmations and that means you'll have to wait ~6 x 2.5 minutes = ~15 minutes to send IX from new addresses which were created by that split. Not that instant
Possible solution is to modify algo:
- to check that none of outputs is greater than 1000 (or whatever spork value is) and not the total tx value (that doesn't solve the problem when change is greater than 1000 though)
- to check that IX have 2 outputs maximum (and give a warning if that's not the case) to allow normal users to pay as usual but to prevent multi IX in single tx at the same time (still can do 2 IX at the same time if you have exact amount but that's and extreme edge case so not a big deal)
M
MangledBlue
Guest
I'm not sure if I'm getting THAT many but I know I've seen a LOT of them
[at work right now so....]
TaoOfSatoshi
Well-known member
Newb question: Why does InstantX require a limit at all if it has the potential to create all of these problems for high-end users?1. Can we change 1000 DASH to a higher value?
Sure it's just another spork which is set to 1000 now.
2. Why can't wallet split huge amounts on IX automatically?
Because we require at leas 6 confirmations and that means you'll have to wait ~6 x 2.5 minutes = ~15 minutes to send IX from new addresses which were created by that split. Not that instant
Possible solution is to modify algo:
- to check that none of outputs is greater than 1000 (or whatever spork value is) and not the total tx value (that doesn't solve the problem when change is greater than 1000 though)
- to check that IX have 2 outputs maximum (and give a warning if that's not the case) to allow normal users to pay as usual but to prevent multi IX in single tx at the same time (still can do 2 IX at the same time if you have exact amount but that's and extreme edge case so not a big deal)
Follow-up comment: I definitely think that there should be some way of cancelling the InstantX tx if it's not going to work, people are not going to like paying .01 (which will be much more value in the future) for nothing.
The original idea of such limits I believe was to lower possible damage from any kind of (un)imaginable attacks while tech is not solid. Remember DS in its early ages? :wink:
TaoOfSatoshi
Well-known member
Oh I see. So it can be removed later. That's good news!
Long time no see.:smile: But it is good to be back (if even for a short while) and see that things are progressing nicely.:grin::grin:
I have a test wallet up and running; it is currently mixing 320 DASH to six rounds and seems to be going smoothly. It is also cpu mining and earned me another 20. At this rate it will take quite a while to get a 1,000 to play with a test masternode. Any donations of tDASH greatly appreciated.
y4VA6inPhhBeoSbfMyad2624N6a6tDCXGi
Peace to you all,
Strix
:grin:I have a test wallet up and running; it is currently mixing 320 DASH to six rounds and seems to be going smoothly. It is also cpu mining and earned me another 20. At this rate it will take quite a while to get a 1,000 to play with a test masternode. Any donations of tDASH greatly appreciated.
y4VA6inPhhBeoSbfMyad2624N6a6tDCXGi
Peace to you all,
Strix
M
MangledBlue
Guest
Long time no see.:smile: But it is good to be back (if even for a short while) and see that things are progressing nicely.:grin:
I have a test wallet up and running; it is currently mixing 320 DASH to six rounds and seems to be going smoothly. It is also cpu mining and earned me another 20. At this rate it will take quite a while to get a 1,000 to play with a test masternode. Any donations of tDASH greatly appreciated.
y4VA6inPhhBeoSbfMyad2624N6a6tDCXGi
Peace to you all,
Strix
There is a faucet link around here somewhere
WELCOME BACK !!!!
edit:
- http://test.faucet.masternode.io - by coingun
- http://test.faucet.dashninja.pl - by elbereth
try these
Sent you 4 ds + ix tx's.Long time no see.:smile: But it is good to be back (if even for a short while) and see that things are progressing nicely.:grin:
I have a test wallet up and running; it is currently mixing 320 DASH to six rounds and seems to be going smoothly. It is also cpu mining and earned me another 20. At this rate it will take quite a while to get a 1,000 to play with a test masternode. Any donations of tDASH greatly appreciated.
y4VA6inPhhBeoSbfMyad2624N6a6tDCXGi
Peace to you all,
Strix
http://test.insight.masternode.io:3...f7e19e141ee79dfdca518a27298d85c6872dd3f962805
http://test.insight.masternode.io:3...f5cc6c6110313a5d0a190b61ef93979d5cfcd91159293
eduffield
Core Developer
Please update -- v0.12.0.4 (version wasn't bumped correctly)
- protocol bump
- Autostart masternode upon startup - eduffield
- added masternode status info (masternode status) - eduffield
- remove unused variable - udjin
- slight optimizations/readability improvements for ds - udjin
- remove unneeded "darkSendPool." in DS pool class functions - udjin
- add missing MSG_ENTRIES_ADDED for proper ds status display -udjin
- move ds pool status out of overview page -udjin
- fix db shutdown crash - adopt btc daf956b - udjin
- Removed PoSe due to consensus issues - eduffield
Linux32:
https://dashpay.atlassian.net/build...n-linux-dash-dist//dash-0.12.0-linux32.tar.gz
Linux64:
https://dashpay.atlassian.net/build...n-linux-dash-dist//dash-0.12.0-linux64.tar.gz
Mac:
https://dashpay.atlassian.net/build...n-osx-dash-dist//dash-0.12.0-osx-unsigned.dmg
Win32:
https://dashpay.atlassian.net/build...1/gitian-win-dash-dist//dash-0.12.0-win32.zip
Win64:
https://dashpay.atlassian.net/build...1/gitian-win-dash-dist//dash-0.12.0-win64.zip
- protocol bump
- Autostart masternode upon startup - eduffield
- added masternode status info (masternode status) - eduffield
- remove unused variable - udjin
- slight optimizations/readability improvements for ds - udjin
- remove unneeded "darkSendPool." in DS pool class functions - udjin
- add missing MSG_ENTRIES_ADDED for proper ds status display -udjin
- move ds pool status out of overview page -udjin
- fix db shutdown crash - adopt btc daf956b - udjin
- Removed PoSe due to consensus issues - eduffield
- With nodes coming and going on the network, the network could come to different opinions about who should get paid next in line due to some nodes being flagged as failing a PoSe check. This will have to be fixed by introducing a blockchain based PoSe system, but that's out of the scope of this release. To fix the issues in the interrim, I'm removing PoSe checks for the time being.
Linux32:
https://dashpay.atlassian.net/build...n-linux-dash-dist//dash-0.12.0-linux32.tar.gz
Linux64:
https://dashpay.atlassian.net/build...n-linux-dash-dist//dash-0.12.0-linux64.tar.gz
Mac:
https://dashpay.atlassian.net/build...n-osx-dash-dist//dash-0.12.0-osx-unsigned.dmg
Win32:
https://dashpay.atlassian.net/build...1/gitian-win-dash-dist//dash-0.12.0-win32.zip
Win64:
https://dashpay.atlassian.net/build...1/gitian-win-dash-dist//dash-0.12.0-win64.zip
Transaction ID: 87f2388eb98482ea37465fa7d77f7bc63497f86c7c743cec7a0cb49aa9fa09ff-000
have a nice day.
M
MangledBlue
Guest
Autostart masternode upon startup - eduffield
NICE !!!!!
Always wanted this :-D
NICE !!!!!
Always wanted this :-D
