salsacz
|
|
January 08, 2014, 05:58:53 PM Last edit: January 08, 2014, 06:43:15 PM by salsacz |
|
|
|
|
|
subSTRATA
Legendary
Offline
Activity: 1288
Merit: 1043
:^)
|
|
January 08, 2014, 05:59:56 PM |
|
Released 0.5.3:
http://download.nxtcrypto.org/nxt-client-0.5.3.zip
sha256: 23fc36fba166e00299003407169a26515e6d67c8094b5a06f9c795cc62ca83a7
Change log:
Fixed blockchain rescanning. Clear unconfirmed transactions on rescan. Not fixed. NXT just did auto-rescan and afterwards 17,653 unconfirmed transactions are still on the list. Machine runs Win7 64-bit.
|
theres nothing here. message me if you want to put something here.
|
|
|
msin
Legendary
Offline
Activity: 1470
Merit: 1004
|
|
January 08, 2014, 06:10:29 PM |
|
Thanks for your work on this!
|
|
|
|
klooch
Newbie
Offline
Activity: 19
Merit: 0
|
|
January 08, 2014, 06:16:29 PM |
|
You are wrong, or maybe you have an agenda? Or just too busy to read ? This was THERE on the DGEX site, FAQ section DGEX promotes NXT trading by lifting trading fees at least in the beta period. We charge 0.9% of all Bitcoin withdrawals to cover transaction fees and other overhead costs. NXT withdrawals carry no fee until the end of 2013, we absorb the 1 NXT transaction fee. Peace.... It's good to see some reasonable behavior in here for a change!
So how much money you wanna rip off this great community and altcoin? 800k NXT not enough, I guess. Fuck off, bastard!It's not just confusing, it's total bullshit. Graviton made for the community more than most of us. If someone doesn't like fees, then remember how much money did you make on Dgex or outside it but because there was such thing as Dgex. If there was no Dgex and nextcoin.org we'd still have Nxt around 0.000001 Btc and one thread here on bitcointalk.
When one do not charge you to get in and later do not allow you to get out for free than it is called a scam. Very simple. On a funny note, check nxt:rawdog Peace! First of all he notified in advance about fees. There was no info on DGEX website. I don't give a shit if he posted it elsewhere. I use his website and I expect info there.27.12.2013: Server migration over, smooth sailing! 16.12.2013: Fee structure change, instant BTC withdrawals available! 08.12.2013: Email server changed, problems should be gone 02.12.2013: NEXT Forum at Nextcoin.org launched! 28.11.2013: Launch of NXT trading. Welcome!
|
|
|
|
greyw00lf
|
|
January 08, 2014, 06:22:29 PM |
|
Your, guys, for some weird reason live in some illusory world, where your code runs on 3 parallel, avionics-grade computers, which then vote on the final result.
In reality your code will run on cheap Chinese memory chips, overheated CPUs and browsers with 24 toolbars installed.
There absolutely must be a way for other nodes to validate the address.
+1! and btw.: gpg: Signature made Wed Jan 8 12:09:11 2014 CET using RSA key ID 3BF9ED80 gpg: Good signature from "Jean-Luc Picard (Lead Developer of The Nxt Generation) <jlp666@yandex.ru>"
|
|
|
|
starik69
Legendary
Offline
Activity: 1367
Merit: 1000
|
|
January 08, 2014, 06:24:06 PM |
|
What does it mean [2014-01-08 19:28:58.571] ...Done
on log?
|
|
|
|
subSTRATA
Legendary
Offline
Activity: 1288
Merit: 1043
:^)
|
|
January 08, 2014, 06:26:06 PM |
|
What does it mean [2014-01-08 19:28:58.571] ...Done
on log? http://www.youtube.com/watch?v=dsx2vdn7gpY
|
theres nothing here. message me if you want to put something here.
|
|
|
klee
Legendary
Offline
Activity: 1498
Merit: 1000
|
|
January 08, 2014, 06:32:45 PM |
|
I HAVE A NEW ASSIGNMENT FOR YOU!!! The IP address is listed as static (which means tellas.gr would have no problem identifying your guy) and is on several spam block lists. He send them! Please delete your post mate, he is clear..
|
|
|
|
plasticAiredale
|
|
January 08, 2014, 06:46:15 PM |
|
I HAVE A NEW ASSIGNMENT FOR YOU!!! The IP address is listed as static (which means tellas.gr would have no problem identifying your guy) and is on several spam block lists. He send them! Please delete your post mate, he is clear.. Damn, rickyjames is like an internet superhero.
|
|
|
|
Jean-Luc
|
|
January 08, 2014, 06:48:51 PM |
|
Released 0.5.3:
http://download.nxtcrypto.org/nxt-client-0.5.3.zip
sha256: 23fc36fba166e00299003407169a26515e6d67c8094b5a06f9c795cc62ca83a7
Change log:
Fixed blockchain rescanning. Clear unconfirmed transactions on rescan. Not fixed. NXT just did auto-rescan and afterwards 17,653 unconfirmed transactions are still on the list. Machine runs Win7 64-bit. Did you reload the page in the browser? I have no plans to fix the GUI to recover by itself on this error.
|
|
|
|
Jean-Luc
|
|
January 08, 2014, 06:49:33 PM |
|
What does it mean [2014-01-08 19:28:58.571] ...Done
on log? That it is done rescanning the blockchain after an error.
|
|
|
|
Jean-Luc
|
|
January 08, 2014, 06:52:14 PM |
|
What happened in the old version when the account number was pasted twice, so it read 1295619013897570058912956190138975700589 ?
In the old version 1295619013897570058912956190138975700589 would be interpreted as 6667516829191161453. Now it gives an error.
|
|
|
|
klee
Legendary
Offline
Activity: 1498
Merit: 1000
|
|
January 08, 2014, 06:56:36 PM |
|
I HAVE A NEW ASSIGNMENT FOR YOU!!! The IP address is listed as static (which means tellas.gr would have no problem identifying your guy) and is on several spam block lists. He send them! Please delete your post mate, he is clear.. Damn, rickyjames is like an internet superhero. When the Boogeyman goes to sleep every night, he checks his closet for Chuck Norris rickyjames.
|
|
|
|
klee
Legendary
Offline
Activity: 1498
Merit: 1000
|
|
January 08, 2014, 06:58:38 PM |
|
Guys, will the decentralized exchange be able to support sports betting? How would this work? Is a third party needed? Could he be in stealth mode?
|
|
|
|
notsoshifty
|
|
January 08, 2014, 07:04:58 PM |
|
So, big players with big wallets and big transaction volumes will end up not paying any fees, whereas the small fish will have to pay fees. Is this a likely scenario, and if so is it a problem?
The outcome is the same as if they paid fees and included not their transactions into forged blocks. I can see that is the case if the block would otherwise be full. In that case, putting your own transactions in and getting/paying zero fees means missing out on a bunch of other people's fees. But if the block you're forging isn't full then you are always best to include as many of your own transactions into your own forged blocks, so you get to perform fee-less transactions. Or is scaling done such that blocks would always be full, once nxt gets full momentum?
|
|
|
|
pandaisftw
|
|
January 08, 2014, 07:05:46 PM |
|
We don't integrate some sort of CRC because of saving a tiny bit of memory in the core code and because sort-of-CRC could be done in a/the client, right?
No, because in the core and when sending across the network the transactions are already signed with the sender public key. Any corruption in the transaction content would automatically invalidate the signature. Sounds reasonable. And what are the options for the client software for user-made input-errors? Spontanious idea: The client software can handle "#account" and "#account"+"account alias" receiver-adresses. The second could be checked by the client before it is signed. It would be convenient and the user felt kinda save. Mmhh, other ideas please? This is actually a really good idea. For large movers, like an exchange, they can require the user to enter their account number and an alias from that account. That would get rid, of all doubt, that the exchange/user made an input error. If there is no memory corruption issue (the devs say that cannot reproduce this), then this system should be golden. The only problem I can see is: if someone buys from an exchange from the first time and does not have an existing account, he can't transfer to any account he wants. A solution is to only apply this account+alias rule to medium-large deposits/withdrawals. So a new user could, say, send 1 NXT to his new, super secure account, register an alias, and then send the rest of his funds with account+alias from the exchange to his account. As for the Account Control, I like the idea of being able to restrict outgoing transactions. I think these two options would be very flexible: - Maximum amount X per Y time-frame
- Timeframe allowed to send funds
With just these two parameters, you can, for example, set X = 0 to completely lock outbound transactions. For everything else, it's more convenient to have a self-defined limit for day-to-day transactions. If one really needs to make a large purchase (uncommon), then they can simply unlock their account, then re-lock after. More choices, I like
|
NXT: 13095091276527367030
|
|
|
mikaljan
|
|
January 08, 2014, 07:09:03 PM Last edit: January 08, 2014, 07:28:07 PM by mikaljan |
|
We need one exchange where we will be able exchange Nxt with LiqPay, WebMoney, QIWI, UKash, IDram, PayWeb, PayPal, EgoPay,Payza,Unionpay,SolidTrustPay,skrill,privat24,hd-money, w1,pecunix,Cosmic Pay,Instaforex, Neteller,pexpay,qiwi, Perfect Money, Paxum, C-gold, OKpay,etc.
Thanks
Mikal
|
|
|
|
bitcoinpaul
|
|
January 08, 2014, 07:10:37 PM |
|
THANK YOU MIKAL
|
|
|
|
subSTRATA
Legendary
Offline
Activity: 1288
Merit: 1043
:^)
|
|
January 08, 2014, 07:13:19 PM |
|
Released 0.5.3:
http://download.nxtcrypto.org/nxt-client-0.5.3.zip
sha256: 23fc36fba166e00299003407169a26515e6d67c8094b5a06f9c795cc62ca83a7
Change log:
Fixed blockchain rescanning. Clear unconfirmed transactions on rescan. Not fixed. NXT just did auto-rescan and afterwards 17,653 unconfirmed transactions are still on the list. Machine runs Win7 64-bit. Did you reload the page in the browser? I have no plans to fix the GUI to recover by itself on this error. Now you confused me. Auto-rescan is supposed to happen or not? If yes, and you won't add GUI auto-recovery, it would be useful to have at least a pop-up saying "Please reload this page to update transaction status" or something similar.
|
theres nothing here. message me if you want to put something here.
|
|
|
bitcoinpaul
|
|
January 08, 2014, 07:15:14 PM |
|
We don't integrate some sort of CRC because of saving a tiny bit of memory in the core code and because sort-of-CRC could be done in a/the client, right?
No, because in the core and when sending across the network the transactions are already signed with the sender public key. Any corruption in the transaction content would automatically invalidate the signature. Sounds reasonable. And what are the options for the client software for user-made input-errors? Spontanious idea: The client software can handle "#account" and "#account"+"account alias" receiver-adresses. The second could be checked by the client before it is signed. It would be convenient and the user felt kinda save. Mmhh, other ideas please? This is actually a really good idea. For large movers, like an exchange, they can require the user to enter their account number and an alias from that account. That would get rid, of all doubt, that the exchange/user made an input error. If there is no memory corruption issue (the devs say that cannot reproduce this), then this system should be golden. The only problem I can see is: if someone buys from an exchange from the first time and does not have an existing account, he can't transfer to any account he wants. A solution is to only apply this account+alias rule to medium-large deposits/withdrawals. So a new user could, say, send 1 NXT to his new, super secure account, register an alias, and then send the rest of his funds with account+alias from the exchange to his account. As for the Account Control, I like the idea of being able to restrict outgoing transactions. I think these two options would be very flexible: - Maximum amount X per Y time-frame
- Timeframe allowed to send funds
With just these two parameters, you can, for example, set X = 0 to completely lock outbound transactions. For everything else, it's more convenient to have a self-defined limit for day-to-day transactions. If one really needs to make a large purchase (uncommon), then they can simply unlock their account, then re-lock after. More choices, I like We lock (locking method not clarified) not the account but all outgoing transactions which would exceed the cumulated outgoing nxt amount in a given time frame. So you can set this amount to whatever you want. (0 = complete 'lock of the account' for example)
|
|
|
|
|