Bitcoin Forum
April 19, 2019, 09:35:59 PM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 [1574] 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 ... 2567 »
  Print  
Author Topic: NXT :: descendant of Bitcoin - Updated Information  (Read 2750621 times)
BloodyRookie
Hero Member
*****
Offline Offline

Activity: 684
Merit: 500


View Profile
February 09, 2014, 06:20:16 PM
 #31461

I've made repo with test:
https://github.com/gimer/curve25519-sign-test

I've also added class files to the repo, so it's enough to replace "nxt-0.7.2\webapps\root\WEB-INF\classes\nxt\crypto\Curve25519.class" with file from the repo and it should work.

I hope that u won't create a "solution" that leaks private key bits. I'm against the changes until I see a formal proof, so u better talk to Jean-Luc.

I don't want to be offensive, but it seems that the curve25519.java file is a black box for you. Talking about leaking private key bits from those changes is ridiculous.
But if BCNext, Jean-Luc and you refuse to make changes to that file then we just have to live with a (in my opinion annoying) every now and then failing signature/verification system.

Nothing Else Matters
NEM: NALICE-LGU3IV-Y4DPJK-HYLSSV-YFFWYS-5QPLYE-ZDJJ
NXT: 11095639652683007953
1555709759
Hero Member
*
Offline Offline

Posts: 1555709759

View Profile Personal Message (Offline)

Ignore
1555709759
Reply with quote  #2

1555709759
Report to moderator
1555709759
Hero Member
*
Offline Offline

Posts: 1555709759

View Profile Personal Message (Offline)

Ignore
1555709759
Reply with quote  #2

1555709759
Report to moderator
1555709759
Hero Member
*
Offline Offline

Posts: 1555709759

View Profile Personal Message (Offline)

Ignore
1555709759
Reply with quote  #2

1555709759
Report to moderator
Remember that Bitcoin is still beta software. Don't put all of your money into BTC!
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
joefox
Full Member
***
Offline Offline

Activity: 210
Merit: 100


View Profile WWW
February 09, 2014, 06:21:35 PM
 #31462


Is this documentation at http://www.thenxtwiki.org/wiki/Nxt_API#Description
already obsolete as there were already several daily updated  from 0.5.11 to 0.7.2?


The documentation for the high-level API is still current (minus a few recent changes that are yet to be updated).  Same API calls that worked on 0.5.11 also work in 0.7.2.

I admin the Nxt Wiki at http://wiki.nxtcrypto.org/ Please support my work by donating to Nxt account #1234567740944417915
wesleyh
Sr. Member
****
Offline Offline

Activity: 308
Merit: 250


View Profile
February 09, 2014, 06:21:45 PM
 #31463

More work has to be done to find someone to do a crypto review.. This really is essential and more pressing than any other development in Nxt.
bitcoinpaul
Hero Member
*****
Offline Offline

Activity: 910
Merit: 1000



View Profile
February 09, 2014, 06:30:13 PM
 #31464

I hope that u won't create a "solution" that leaks private key bits. I'm against the changes until I see a formal proof, so u better talk to Jean-Luc.

Well, I understand math behind the change. (Please, spend 5 min, to read original BloodyRookie's post).

The ONLY difference to original sign is that (x-h) is represented correctly.
(and it WON'T leak keys, attacker would STILL need to solve DLP problem in that group:
 or in other words, if s is priv key, what is the difference between a*s and a'*s)

I'm going to run NRS with patched Curve from now on.

edit: some more explanation here: https://nextcoin.org/index.php/topic,3915.0.html

There are 2 options:

1. Patch Curve25519 class
2. Patch Crypto class

Option 1, unlike option 2, may lead to problems u can't even imagine. I would patched Crypto...

+1

I'm no dev, but please don't touch curve.
bitcoinpaul
Hero Member
*****
Offline Offline

Activity: 910
Merit: 1000



View Profile
February 09, 2014, 06:30:39 PM
 #31465

Here is version 1.7 of my Windows NXT client "NXT Solaris".

The (future) open-source version now has the everything implemented that the closed-source version has (except for the blockchain explorer which won't be available in the open-source version).

...

Donations
I hope you like my client and I’d be extremely happy to see some donations for the future of this project!

NXT: 1758531264253431177

Nice!
Fatih87SK
Hero Member
*****
Offline Offline

Activity: 616
Merit: 500



View Profile
February 09, 2014, 06:37:11 PM
 #31466

Here is version 1.7 of my Windows NXT client "NXT Solaris".

The (future) open-source version now has the everything implemented that the closed-source version has (except for the blockchain explorer which won't be available in the open-source version).

...

Donations
I hope you like my client and I’d be extremely happy to see some donations for the future of this project!

NXT: 1758531264253431177

Nice!

Awesome!

Come-from-Beyond
Legendary
*
Offline Offline

Activity: 2086
Merit: 1007

Newbie


View Profile
February 09, 2014, 06:41:51 PM
 #31467

I don't want to be offensive, but it seems that the curve25519.java file is a black box for you. Talking about leaking private key bits from those changes is ridiculous.
But if BCNext, Jean-Luc and you refuse to make changes to that file then we just have to live with a (in my opinion annoying) every now and then failing signature/verification system.

Common sense doesn't work in cryptography. The problem is easily solvable by another way, so everyone who uses ur fix is just looking for troubles.

The statement that changes in Curve25519 can't lead to private key leakage still require a proof. If u can't provide the math, then u should prove that current implementation was incorrectly translated into Java from the original.
bitcoinpaul
Hero Member
*****
Offline Offline

Activity: 910
Merit: 1000



View Profile
February 09, 2014, 06:42:03 PM
 #31468

I've started a section on the wiki for organizing our projects. In particular, check out the List of Proposals and Bounties page. I'm thinking we could link to stuff that is "active" there. That could be links to forum threads, google docs, or other wiki pages where projects are being discussed and hashed out, and project statuses are being updated.

For a good example of this, check out the wiki page for the new address format using Reed-Solomon encoding that NxtChg started a long time ago. Very clearly organized.

My thinking is to use the Discussion pages for throwing around ideas, criticisms, suggestions, etc, and use the main pages for summary of the proposal/project status.

Not enough folks are using Discussion pages . Click on this tab more often:



James, this could be the right place for you to put up your (many, many!) ideas for comment. EvilDave, you could put your carbon offset proposal here too. Lots more projects that I don't remember (this is why we need to put all of them in a convenient place).

Pin, maybe it could be easier if you got everyone to post their projects on the wiki instead? Then you can just go through a list of links.

Don't worry about messing things up, it's a wiki, everything can be reversed. And don't worry if you don't know wiki formatting, just type/copy and paste. Other people can help you clean things up. If there's demand, I'll put up a quick guide to simple wiki editing.

I'll be technical support. Anyone has a problem, e.g. getting errors, can't figure out how to do something, ask me and I'll troubleshoot.

+1000

At least, put all your ideas and projects into this wiki. We need this! Nxt needs this!



absolutely the right thought,
but maybe this:  List of Proposals and Bounties page
is interfering with:  http://wiki.nxtcrypto.org/wiki/Planned_Features

I think we should have ONE place not to waste much time for synchronizing it later?
What do you think?

cheers

But we have

- planned features (http://wiki.nxtcrypto.org/wiki/Planned_Features)
- a big think box which contains all ideas with their possible consequences, and thoughts about target audiences (http://wiki.nxtcrypto.org/wiki/List_of_Proposals)

First one should be more clear and short, the second is more a collection and discussion point which can change several times daily.

We should keep both. What do the others think?

And:
What do others think in general about a / this place for discussion about possible features, service providers and target audiences?
martismartis
Legendary
*
Offline Offline

Activity: 1162
Merit: 1005


View Profile
February 09, 2014, 06:43:24 PM
Last edit: February 09, 2014, 07:01:57 PM by martismartis
 #31469

NXTsolaris doesn't run in PC at all. Even I cannot close it in normal way.

EDIT: running finally.
fmiboy
Full Member
***
Offline Offline

Activity: 189
Merit: 100


View Profile
February 09, 2014, 06:59:32 PM
 #31470


Is this documentation at http://www.thenxtwiki.org/wiki/Nxt_API#Description
already obsolete as there were already several daily updated  from 0.5.11 to 0.7.2?


The documentation for the high-level API is still current (minus a few recent changes that are yet to be updated).  Same API calls that worked on 0.5.11 also work in 0.7.2.

some are missing, but once you start using them more often, you will figure out from error messages what each query/API call needs.
bitcoinpaul
Hero Member
*****
Offline Offline

Activity: 910
Merit: 1000



View Profile
February 09, 2014, 07:02:11 PM
 #31471

I've seen a couple of forging pools throughout this thread and noticed a possibitly of forging only by giving "forging rights" without giving the NXTs.

Has anyone one of you tried this and which pool did you use?

I am pretty sure that possibility was only discussed, it is not possible yet

Maybe this gets implemented in Account Control, which is developed by BCNext himself right now.
smartwart
Full Member
***
Offline Offline

Activity: 171
Merit: 100


View Profile
February 09, 2014, 07:09:09 PM
 #31472

I've started a section on the wiki for organizing our projects. In particular, check out the List of Proposals and Bounties page. I'm thinking we could link to stuff that is "active" there. That could be links to forum threads, google docs, or other wiki pages where projects are being discussed and hashed out, and project statuses are being updated.

For a good example of this, check out the wiki page for the new address format using Reed-Solomon encoding that NxtChg started a long time ago. Very clearly organized.

My thinking is to use the Discussion pages for throwing around ideas, criticisms, suggestions, etc, and use the main pages for summary of the proposal/project status.

Not enough folks are using Discussion pages . Click on this tab more often:



James, this could be the right place for you to put up your (many, many!) ideas for comment. EvilDave, you could put your carbon offset proposal here too. Lots more projects that I don't remember (this is why we need to put all of them in a convenient place).

Pin, maybe it could be easier if you got everyone to post their projects on the wiki instead? Then you can just go through a list of links.

Don't worry about messing things up, it's a wiki, everything can be reversed. And don't worry if you don't know wiki formatting, just type/copy and paste. Other people can help you clean things up. If there's demand, I'll put up a quick guide to simple wiki editing.

I'll be technical support. Anyone has a problem, e.g. getting errors, can't figure out how to do something, ask me and I'll troubleshoot.

+1000

At least, put all your ideas and projects into this wiki. We need this! Nxt needs this!



absolutely the right thought,
but maybe this:  List of Proposals and Bounties page
is interfering with:  http://wiki.nxtcrypto.org/wiki/Planned_Features

I think we should have ONE place not to waste much time for synchronizing it later?
What do you think?

cheers

But we have

- planned features (http://wiki.nxtcrypto.org/wiki/Planned_Features)
- a big think box which contains all ideas with their possible consequences, and thoughts about target audiences (http://wiki.nxtcrypto.org/wiki/List_of_Proposals)

First one should be more clear and short, the second is more a collection and discussion point which can change several times daily.

We should keep both. What do the others think?

And:
What do others think in general about a / this place for discussion about possible features, service providers and target audiences?



so we have two options:

1. to have planned features (http://wiki.nxtcrypto.org/wiki/Planned_Features) with final description
    and a big think box which contains all ideas (http://wiki.nxtcrypto.org/wiki/List_of_Proposals)

2. to have planned features (http://wiki.nxtcrypto.org/wiki/Planned_Features) with final description
    - extended by a sub topic "Think Box"

In general, could the discussion Tab from Planned Features be the Think Box?

In any case we should restructure the "Planned_Features" to have just the feature as a link.
Behind that link we find the description of that specific feature.
The "Account Control" Page could be the reference for the detailed description.

That would make it well structured like:
+ Feature Name =link=> Detailed Description Page like.   (same as already for Account Control)

NxT: 13574045486980287597
Bitventurer
Sr. Member
****
Offline Offline

Activity: 488
Merit: 250

S P 8 D E


View Profile WWW
February 09, 2014, 07:16:17 PM
 #31473





Awesome!

can you design the cells in the chain ?

SP8DE - The Game of Chance. Changed.
Come-from-Beyond
Legendary
*
Offline Offline

Activity: 2086
Merit: 1007

Newbie


View Profile
February 09, 2014, 07:18:11 PM
 #31474

Unclaimed coins have been transferred to the keepers

2'904'675 NXT was sent to each of the accounts:

http://localhost:7874/nxt?requestType=getTransaction&transaction=8229158905562123840
http://localhost:7874/nxt?requestType=getTransaction&transaction=419112573708720396
http://localhost:7874/nxt?requestType=getTransaction&transaction=818794594833884287

PS: Only 100k left on the account controlled by me. It will be used to pay the reward for the injected fatal flaw. All other rewards/bounties must be paid from the accounts controlled by the keepers.

gimre
Legendary
*
Offline Offline

Activity: 857
Merit: 1000



View Profile WWW
February 09, 2014, 07:41:00 PM
 #31475

There are 2 options:

1. Patch Curve25519 class
2. Patch Crypto class

Option 1, unlike option 2, may lead to problems u can't even imagine. I would patched Crypto...

There is no way you can patch Crypto.sign. (or it would be bloody dumb)

Common sense doesn't work in cryptography. The problem is easily solvable by another way, so everyone who uses ur fix is just looking for troubles.

The statement that changes in Curve25519 can't lead to private key leakage still require a proof. If u can't provide the math, then u should prove that current implementation was incorrectly translated into Java from the original.

It's not about common sense, it's about knowing and understanding underlying problems.

Let s be your secret/priv key.
public key is nothing more than G*s in very specific finite field.

Finding priv key, while having public key == DLP on elliptic curve.

NOW, signing is actually:
v * temp, where temp is related ONLY to PUBLIC key. (v is dependent ONLY on the data)

What BloodyRookie's patch does is changing v into v' and changing the above to:
v' * temp

This leads to following OBVIOUS implication:

If OLD/original sign() doesn't leak private key bits =then=> PATCHED sign() doesn't leak them.

(whatever old one leaks is up to you, I know it doesn't, cause it's NOT related directly to private key)

Come-from-Beyond
Legendary
*
Offline Offline

Activity: 2086
Merit: 1007

Newbie


View Profile
February 09, 2014, 07:45:34 PM
 #31476

There is no way you can patch Crypto.sign. (or it would be bloody dumb)

Why do u think so?
garp
Member
**
Offline Offline

Activity: 94
Merit: 10


View Profile
February 09, 2014, 07:54:49 PM
 #31477

NXT is 100% proof of stake and uses something called transparent forging instead of mining. Transparent forging allows you to predict which forgers will author upcoming blocks and if you trust those forgers than your transactions can be thought of as instantly secure. If you dont trust them than its still faster than bitcoin with 1 minute confirmations. Unlike fast coin or min coin though these 1 minute blocks actually add security similar in strength similar to bitcoins 10 minute confirmations. The fact that we dont rely on mining means that huge amounts of resources are saved in securing the blockchain. This means that transactions can still be secure at a fraction of the fee of mined coins. We also take a data driven approach to transactions rather than using scrypts which will allow visa level transaction volume when the need arises. Our devs are implementing decentralized asset exchange later this month! Stick around and keep reading and learning. There is a lot to learn about nxt and a lot that is worth learning. This is not your average copycat coin and you are very early to this party indeed.

Very well and clearly explained.
Although I'm trying to keep up with this thread since 2013, still usefull for myself as well  Smiley

Thank you.

garp
gimre
Legendary
*
Offline Offline

Activity: 857
Merit: 1000



View Profile WWW
February 09, 2014, 08:00:30 PM
 #31478

There is no way you can patch Crypto.sign. (or it would be bloody dumb)

Why do u think so?

Let's say you have leaking tap.

Patching Crypto.sign is like putting bucket under the tap instead of fixing the tap itself...

scor2k
Legendary
*
Offline Offline

Activity: 1001
Merit: 1001


work hard, die young (c)


View Profile WWW
February 09, 2014, 08:01:42 PM
 #31479

Hello!

My project is Wordpress plugin, that allow log in with NXT token. Plugin name nxtAuth .

How it's works:
  • Click on the image with NXT logo and enter valid NXT token
  • If NXT server online and token valid - you log in to site with subscriber account
  • On the Wordpress settings page you can change address of NXT server. By default - localhost

ToDo:
  • Adding modal jQuery window
  • Add User page with additional Info, such as transactions, etc
  • Integrate with my AM project - http://nxtdb.info

How to test:
  • Go to http://nxtdb.info and click "Authenticate with NXT token" in header
  • On the top-right corner click logo and enter valid (or not) NXT token for site: nxtdb.info
  • Or you can install this plugin on your Wordpress blog. Find nxtAuth plugin, install and activate it.


Bug report:
If you find some bug, send me PM with description and I pay you 100 NXT Smiley

P.S. Sorry for my bad english Smiley
l8orre
Legendary
*
Offline Offline

Activity: 1045
Merit: 1002


View Profile
February 09, 2014, 08:11:39 PM
 #31480


For raspi (model B) use settings:



       SNl    0:34 /usr/bin/java -Xms128m -Xmx756m -jar start.jar STOP.PORT=7873 S

works fine - a common error I made usually is to set it at 450/450 or so - that limits the heap space to 450MB, which is NOT enough!

Xms128 is the MINIMUM heap size,

Xmx756 is the MAXIMUM, presto!
Pages: « 1 ... 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 [1574] 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 ... 2567 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!