JulioCesar
Member
Offline
Activity: 64
Merit: 10
|
|
October 14, 2014, 07:52:30 PM |
|
BTer re-open the BTC-NFD trade.
Good news, but there is only one exchange for Nfd? We are working to get listed on a second exchange. that would be great! From which exchange are you talking about? hitbtc, we will provide two market makers to get listed. Do you have news about listing on hitbtc.com? push
|
1b7150efc4abdc96f11a0b678d974541318a4a7973e0588d4849651551963a7d
|
|
|
Nxtblg
Legendary
Offline
Activity: 924
Merit: 1000
|
|
October 14, 2014, 10:14:33 PM |
|
BTer re-open the BTC-NFD trade.
Good news, but there is only one exchange for Nfd? We are working to get listed on a second exchange. that would be great! From which exchange are you talking about? hitbtc, we will provide two market makers to get listed. Do you have news about listing on hitbtc.com? Not yet. As of the last I heard from them, we're still on their waiting list. I just sent a status-update request.
|
|
|
|
xibeijan
Legendary
Offline
Activity: 1232
Merit: 1001
|
|
October 14, 2014, 10:37:15 PM |
|
I see two other problems. An attacker could issue a feed with a malicus link to a new java exploit and kill the network. Every forging node have to make requests to an external web site. Users who wants to stay anonym could have a problem with that.
I don't agree that any of the things you've pointed out are actually issues. This last one is obviously not an issue, since to be malicious the links contents would have to be run as javascript to result in an exploit. In terms of anonymity, the forger would simply opt-out of verifying feed txs. But if someone wants to be anonymous then they should probably not be using a NXT-based cryptocurrency altogether.
|
|
|
|
MaWo (OP)
|
|
October 15, 2014, 02:07:35 PM Last edit: October 15, 2014, 02:49:28 PM by MaWo |
|
I see two other problems. An attacker could issue a feed with a malicus link to a new java exploit and kill the network. Every forging node have to make requests to an external web site. Users who wants to stay anonym could have a problem with that.
I don't agree that any of the things you've pointed out are actually issues. This last one is obviously not an issue, since to be malicious the links contents would have to be run as javascript to result in an exploit. In terms of anonymity, the forger would simply opt-out of verifying feed txs. But if someone wants to be anonymous then they should probably not be using a NXT-based cryptocurrency altogether. I have to identify all issues even long-term issues. The current approach has many problems. A more secure approach is to only depend on special feed transactions of an account. The account owner is responsible for correct values. It's the same trust model like assets are using. If an asset issuer promise to pay a dividend then you have to believe it. A feed transaction is only syntactical verified by nodes. You must trust the feed issuer that she/he delivers correct values and is not gaming. To reduce this trust problem, the NFD dev team could run some common feeds. If the service is temporary unavailable and bids can not be solved because of missing information, all affected bids are canceled. Every party lose only their transaction fee.
|
|
|
|
Nxtblg
Legendary
Offline
Activity: 924
Merit: 1000
|
|
October 15, 2014, 05:48:47 PM |
|
I see two other problems. An attacker could issue a feed with a malicus link to a new java exploit and kill the network. Every forging node have to make requests to an external web site. Users who wants to stay anonym could have a problem with that.
I don't agree that any of the things you've pointed out are actually issues. This last one is obviously not an issue, since to be malicious the links contents would have to be run as javascript to result in an exploit. In terms of anonymity, the forger would simply opt-out of verifying feed txs. But if someone wants to be anonymous then they should probably not be using a NXT-based cryptocurrency altogether. I have to identify all issues even long-term issues. The current approach has many problems. A more secure approach is to only depend on special feed transactions of an account. The account owner is responsible for correct values. It's the same trust model like assets are using. If an asset issuer promise to pay a dividend then you have to believe it. A feed transaction is only syntactical verified by nodes. You must trust the feed issuer that she/he delivers correct values and is not gaming. To reduce this trust problem, the NFD dev team could run some common feeds. If the service is temporary unavailable and bids can not be solved because of missing information, all affected bids are canceled. Every party lose only their transaction fee. Yes, that's what I was thinking too...to the point of looking at this Website: http://www.financialcontent.com/services/online/widget_examples.php Financial Content is a reputable service: I looked into it long ago.
|
|
|
|
jackychan
Full Member
Offline
Activity: 189
Merit: 100
The future will be Digital
|
|
October 17, 2014, 05:15:47 PM |
|
Any news about NFD? the price drop to 1satoshi in BTer now, so sad, we need blood
|
|
|
|
MaWo (OP)
|
|
October 18, 2014, 01:30:11 AM |
|
Any news about NFD? the price drop to 1satoshi in BTer now, so sad, we need blood I hope to find the time to release NFD-1.2.9 this weekend.
|
|
|
|
jackychan
Full Member
Offline
Activity: 189
Merit: 100
The future will be Digital
|
|
October 18, 2014, 02:04:35 AM |
|
Any news about NFD? the price drop to 1satoshi in BTer now, so sad, we need blood I hope to find the time to release NFD-1.2.9 this weekend. Thanks MaWo, I will keep an eye on the new release, will update the client when the new client release, thanks for the great job, hope the NFD alive for next couple of decades
|
|
|
|
l8orre
Legendary
Offline
Activity: 1181
Merit: 1018
|
|
October 18, 2014, 04:01:35 AM |
|
Any news about NFD? the price drop to 1satoshi in BTer now, so sad, we need blood I hope to find the time to release NFD-1.2.9 this weekend. Thanks a lot for being so up to date - I think this is a crucial update! Then, with 1.3.1, it will not be so urgent to update too soon, plenty of time to let it mature a bit.
|
|
|
|
MaWo (OP)
|
|
October 19, 2014, 12:56:00 AM |
|
NFD NSC asset transferred. 2014-10-19 00:47:06 UTC INFO: In total 5338 assets transferred to 30 different accounts NFD-54K9-EEHD-66FP-FKNCA 1700 NFD-2U27-U3XW-NFL9-ABNR3 547 NFD-KFKX-DP6F-8E4M-28T9Q 443 NFD-HJGQ-W4PY-YM3P-682XB 421 NFD-MXSL-RCHX-JZ5M-6AUZ2 367 NFD-4JLG-2495-U2SM-DAEZQ 362 NFD-CBLT-8TCH-WDWJ-AWWBQ 241 NFD-WZ6A-MJRT-F7FU-9X6N8 213 NFD-6TG6-NT24-SHSB-G4LNB 209 NFD-LNE5-PXJK-U99X-5MW4Y 188 NFD-JLTR-7JE5-FVDD-DR9SG 183 NFD-RN9N-3YB7-6HAN-BKDKV 102 NFD-QNEN-T672-V9DS-7MUEP 101 NFD-SMNX-G8AE-HHX6-D8CNH 56 NFD-ZBMU-MW7Q-AJ6G-GT9GT 54 NFD-G94C-SP3P-3UYA-8WN36 30 NFD-83UM-MYKZ-JGNC-7PBXM 23 NFD-C3TP-7273-XRJF-EWSBK 20 NFD-AARK-7F25-QPUW-DBUFM 15 NFD-4H5C-ZJBD-CQM7-5J9VA 14 NFD-ZQAH-VEJ9-FVNK-B94RN 10 NFD-7PKG-UY33-8WPZ-CAZKG 9 NFD-FZJ9-2E3X-2TAW-DUHP2 8 NFD-WKDW-YW7X-QZMQ-EQDDF 7 NFD-UD7F-8AXC-LL8G-7SAKR 7 NFD-EJ4T-2VXA-C3YM-4RDZV 3 NFD-FDTN-DN29-FTBP-D2ZYV 2 NFD-CL58-9S9R-BQXF-BWWNU 1 NFD-CGYV-TMQK-48SP-92L3L 1 NFD-7268-8XUF-BK6F-8HAS6 1
|
|
|
|
peterpanda
|
|
October 19, 2014, 12:44:04 PM |
|
Hi, every one. The dividend for TMCasset of the 1st week have been send: accountRS accountID asset NFD TransID NFD-HUTS-XUPH-93T5-FAAWU 15956544775913990968 5 217.5 1741376435961263108 NFD-54K9-EEHD-66FP-FKNCA 15288191739965311527 100 4350 8498607535095972922 NFD-ZBMU-MW7Q-AJ6G-GT9GT 17057658050152736378 40 1740 8132197090020074829 NFD-2U27-U3XW-NFL9-ABNR3 9286011010206951429 10 435 7790497503476148348 NFD-TJW5-CZPV-A8M8-FVSY6 15166746234531398531 60 2610 8354195344898194359 May you all have a good weekend The dividend for TMCasset of the 2nd week have been send: accountRS asset NFD TxID NFD-HUTS-XUPH-93T5-FAAWU 5 262.625 16615057866387148704 NFD-54K9-EEHD-66FP-FKNCA 100 5271.5 9163123136025345715 NFD-ZBMU-MW7Q-AJ6G-GT9GT 60 3162.5 17587038369114376099 NFD-2U27-U3XW-NFL9-ABNR3 100 5271.5 7221254545450480570 NFD-TJW5-CZPV-A8M8-FVSY6 60 3162.5 10132492848393507506 NFD-6TG6-NT24-SHSB-G4LNB 15 789.875 15504953221131057706 Detail information can be found from: https://bitcointalk.org/index.php?topic=793647.0The dividend for TMCasset of the 3rd week have been send: accountRS asset NFD TxID NFD-HUTS-XUPH-93T5-FAAWU 5 184.25 12777114153027744945 NFD-54K9-EEHD-66FP-FKNCA 100 3704 9196265133973410551 NFD-ZBMU-MW7Q-AJ6G-GT9GT 60 2222 10761864753115237427 NFD-2U27-U3XW-NFL9-ABNR3 100 3704 16165746790174565270 NFD-TJW5-CZPV-A8M8-FVSY6 60 2222 5143460247054048627 NFD-6TG6-NT24-SHSB-G4LNB 15 554.75 13354127218095285587 NFD-LNE5-PXJK-U99X-5MW4Y 1 36.05 337640623145427427 NFD-FDTN-DN29-FTBP-D2ZYV 5 184.25 14705068123072978444 The dividend for TMCasset of the 4th week have been send: accountRS asset NFD TxID NFD-HUTS-XUPH-93T5-FAAWU 5 128.25 3976319930580840457 NFD-54K9-EEHD-66FP-FKNCA 100 2565 3976319930580840457 NFD-ZBMU-MW7Q-AJ6G-GT9GT 60 1539 4483493912378454660 NFD-2U27-U3XW-NFL9-ABNR3 100 2565 15024413585570847697 NFD-TJW5-CZPV-A8M8-FVSY6 60 1539 1716707366181513718 NFD-6TG6-NT24-SHSB-G4LNB 15 384.75 8847847428813363099 NFD-LNE5-PXJK-U99X-5MW4Y 9 230.85 14158676417727302629 NFD-FDTN-DN29-FTBP-D2ZYV 5 128.25 13761544404117636548
|
|
|
|
MaWo (OP)
|
|
October 20, 2014, 01:07:43 AM Last edit: October 20, 2014, 01:38:51 AM by MaWo |
|
New NFD client release nfd-client-NFD-1.2.9.zipThis release includes a critical bugfix. Everyone using NFD 1.2.6 or earlier should upgrade! As second it's no longer allowed to create pre-DGS block transactions (pre NFD-1.2.6 client transactions). Such transactions from a forked client will be ignored!NFD 1.2.9 changelog: - New API request getRichList. Example: http://localhost:8876/nxt?requestType=getRichList
- New API request getAllAccountIds. Example: http://localhost:8876/nxt?requestType=getAllAccountIds
- Fixed a wrong jquery reference which prevented the block explorer from working
- Enabling re-validation of blocks and transactions at start (nxt.forceValidate=true). Validation will be disabled again with 1.3.x release.
- Critical bugfix release (please see nxt-client-1.2.9.changelog.txt) Everyone using NFD 1.2.6 or earlier should upgrade!
- Version scheme changed to NXT like version scheme
- NFD NSC asset transfer tool as code example
Merged all enhancements and bugfixes from NXT. Please look at the NXT client changelog files for details:
|
|
|
|
peterpanda
|
|
October 20, 2014, 01:57:49 AM |
|
great work, thank you very much
|
|
|
|
jackychan
Full Member
Offline
Activity: 189
Merit: 100
The future will be Digital
|
|
October 20, 2014, 08:48:58 AM |
|
Great, mawo, you did a great job. i am going to update the client.
|
|
|
|
Nxtblg
Legendary
Offline
Activity: 924
Merit: 1000
|
|
October 20, 2014, 01:05:28 PM |
|
MaWo actually did a lot of work on this - I'm glad I'm not the first to thank him.
|
|
|
|
thc4me
Member
Offline
Activity: 93
Merit: 10
|
|
October 24, 2014, 07:57:36 AM |
|
I upgraded my client and when I open my wallet the NFD-1.2.9 shows up but it also says NRS version outdated. I have clicked on the NRS update and dropped the 1.2.9 zip file onto window, nothing happens. I have also clicked pick file and selected it but the wallet still says NRS outdated.
How do I fix this? Thanks in advance.
|
|
|
|
l8orre
Legendary
Offline
Activity: 1181
Merit: 1018
|
|
October 24, 2014, 08:09:38 AM |
|
I upgraded my client and when I open my wallet the NFD-1.2.9 shows up but it also says NRS version outdated. I have clicked on the NRS update and dropped the 1.2.9 zip file onto window, nothing happens. I have also clicked pick file and selected it but the wallet still says NRS outdated.
How do I fix this? Thanks in advance.
I am not 100% sure, but this MAY relate to the 1.2.9 <-> 1.3.1 versions. 1.2.9 is very stable and there is no hurry to go to 1.3.1, so I think you can ignore this until NFD goes to 1.3.1 (please correct me if I am wrong there anybody!) The NXT version of 1.3.1 includes some irreversible changes and is currently being thoroughly test by the NXT'ers, and it has always been MaWos prudent approach to not introduce changes too hastily!
|
|
|
|
thc4me
Member
Offline
Activity: 93
Merit: 10
|
|
October 24, 2014, 08:15:23 AM Last edit: October 24, 2014, 08:40:02 AM by thc4me |
|
I upgraded my client and when I open my wallet the NFD-1.2.9 shows up but it also says NRS version outdated. I have clicked on the NRS update and dropped the 1.2.9 zip file onto window, nothing happens. I have also clicked pick file and selected it but the wallet still says NRS outdated.
How do I fix this? Thanks in advance.
I am not 100% sure, but this MAY relate to the 1.2.9 <-> 1.3.1 versions. 1.2.9 is very stable and there is no hurry to go to 1.3.1, so I think you can ignore this until NFD goes to 1.3.1 (please correct me if I am wrong there anybody!) The NXT version of 1.3.1 includes some irreversible changes and is currently being thoroughly test by the NXT'ers, and it has always been MaWos prudent approach to not introduce changes too hastily! Thanks for the response.... Found the answer to how to fix: After installing 1.2.9, set nxt.forceValidate=true in nxt.properties and restart, to force a revalidation of blocks already in the database. Set this property back to false after the first run. Just tested this and it works fine. No more outdated issue.
|
|
|
|
MaWo (OP)
|
|
October 24, 2014, 08:55:05 AM |
|
I upgraded my client and when I open my wallet the NFD-1.2.9 shows up but it also says NRS version outdated. I have clicked on the NRS update and dropped the 1.2.9 zip file onto window, nothing happens. I have also clicked pick file and selected it but the wallet still says NRS outdated.
How do I fix this? Thanks in advance.
This is a browser cache issue. You only need to delete the cache of your browser.
|
|
|
|
Nxtblg
Legendary
Offline
Activity: 924
Merit: 1000
|
|
October 24, 2014, 03:21:57 PM |
|
I upgraded my client and when I open my wallet the NFD-1.2.9 shows up but it also says NRS version outdated. I have clicked on the NRS update and dropped the 1.2.9 zip file onto window, nothing happens. I have also clicked pick file and selected it but the wallet still says NRS outdated.
How do I fix this? Thanks in advance.
This is a browser cache issue. You only need to delete the cache of your browser. Yes, that's what he wrote to me earlier and it worked.
|
|
|
|
|