Bitcoin Forum
October 06, 2022, 01:16:43 AM *
News: Latest Bitcoin Core release: 23.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 [2062] 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 ... 2557 »
  Print  
Author Topic: NXT :: descendant of Bitcoin - Updated Information  (Read 2761319 times)
ChuckOne
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250

☕ NXT-4BTE-8Y4K-CDS2-6TB82


View Profile
March 06, 2014, 04:18:42 PM
 #41221

Something, I would like to add to the discussion of finding consensus.

What makes the difference between a malicious 90% forger and the rest of the world is that these forger simply CAN exclude or include transactions at will as could do any other node.

Problem with analyzing included transactions is: we cannot find consensus by looking at them because we have yet to agree on them.

The only feasible way (if there is one) is analyzing the block graph.

I hope that make the problem more clear.
1665019003
Hero Member
*
Offline Offline

Posts: 1665019003

View Profile Personal Message (Offline)

Ignore
1665019003
Reply with quote  #2

1665019003
Report to moderator
1665019003
Hero Member
*
Offline Offline

Posts: 1665019003

View Profile Personal Message (Offline)

Ignore
1665019003
Reply with quote  #2

1665019003
Report to moderator
1665019003
Hero Member
*
Offline Offline

Posts: 1665019003

View Profile Personal Message (Offline)

Ignore
1665019003
Reply with quote  #2

1665019003
Report to moderator
"You Asked For Change, We Gave You Coins" -- casascius
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1665019003
Hero Member
*
Offline Offline

Posts: 1665019003

View Profile Personal Message (Offline)

Ignore
1665019003
Reply with quote  #2

1665019003
Report to moderator
1665019003
Hero Member
*
Offline Offline

Posts: 1665019003

View Profile Personal Message (Offline)

Ignore
1665019003
Reply with quote  #2

1665019003
Report to moderator
1665019003
Hero Member
*
Offline Offline

Posts: 1665019003

View Profile Personal Message (Offline)

Ignore
1665019003
Reply with quote  #2

1665019003
Report to moderator
opticalcarrier
Full Member
***
Offline Offline

Activity: 238
Merit: 100



View Profile
March 06, 2014, 04:23:21 PM
 #41222

or could we revisit the idea about the possibiliy of a TF algorithm that would support 2 or 3 different accounts that could forge the next block?  and possibly make it such that if an account forged a block then the algorithm would reduce its potential for the next block?  just throwing out ideas. 
ChuckOne
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250

☕ NXT-4BTE-8Y4K-CDS2-6TB82


View Profile
March 06, 2014, 04:23:24 PM
Last edit: March 06, 2014, 04:42:47 PM by ChuckOne
 #41223

I was think about the 1-block-per-minute regime:

The network has 1 minute to agree on a block.

Let the n first accounts in the forging queue create a block on their own and distribute it to the network.

Each node will decide independently which is the best block for it (depending on the network latency). That is, the block with the first forger in the queue that created a block is accepted.

After that minute, a new set of n blocks are created as it was for the first minute.

If now the malicious forger sends his block from the first minute to the network, it's over for him. Nobody will accept it anymore as the second minute has already started.


*EDIT*: forging queue: for each block there is a queue of ALL accounts. The first one is the best one, the second one is the second-best and so on. If a node receives a block, it decided whether that block is within that minute AND whether it's better than nothing or the other blocks it has already received. This queue changes with every block pseudo-randomly.
marcus03
Full Member
***
Offline Offline

Activity: 224
Merit: 100


View Profile
March 06, 2014, 04:30:41 PM
 #41224

Can a Mac dev help me out?

How would I enable the user to start my client with a command line parameter on OSX?

On Windows, if my client is started with "NxtSolarisFM.exe testnet" it will connect the NXT testnet and use different files.

For OSX I distribute a zip file with a "NXTSolaris.app" folder in it. Could I add a script or something that would make it easy (like clicking on it...) for the Mac user to run it with the "testnet" parameter?
Come-from-Beyond
Legendary
*
Offline Offline

Activity: 2142
Merit: 1009

Newbie


View Profile
March 06, 2014, 04:33:11 PM
 #41225

Hmm... I am not quite clear on what you are referring to as being the "latest target" - if this is something to do with "difficulty" then my understanding from discussions with CfB about TF is that it won't even be necessary to have that (I am not even quite sure why "difficulty" was even used at all - perhaps someone would care to enlighten me?).

Difficulty defines bias toward bigger accounts. Set it lower and 10M account will forge 1.1% of all blocks. Set it higher and the account will forge only 1.05%.
CIYAM
Legendary
*
Offline Offline

Activity: 1890
Merit: 1028


Ian Knowles - CIYAM Lead Developer


View Profile WWW
March 06, 2014, 04:41:34 PM
 #41226

Difficulty defines bias toward bigger accounts. Set it lower and 10M account will forge 1.1% of all blocks. Set it higher and the account will forge only 1.05%.

So if we limited the forging power of a single account to x then presumably the "difficulty" would become practically irrelevant.

With CIYAM anyone can create 100% generated C++ web applications in literally minutes.

GPG Public Key | 1ciyam3htJit1feGa26p2wQ4aw6KFTejU
CIYAM
Legendary
*
Offline Offline

Activity: 1890
Merit: 1028


Ian Knowles - CIYAM Lead Developer


View Profile WWW
March 06, 2014, 04:45:29 PM
 #41227

or could we revisit the idea about the possibiliy of a TF algorithm that would support 2 or 3 different accounts that could forge the next block?  and possibly make it such that if an account forged a block then the algorithm would reduce its potential for the next block?  just throwing out ideas.  

Effectively that is the original TF idea from BCNext (AFAIK) - 2 or 3 (or 4?) accounts would get *equal* ability to forge the next block and those that *fail* are *penalised* for not doing so (am not quite sure if the penalty is intended just for those that fail to broadcast or what and maybe this is why I am not convinced about the *penalty* thing so far).

With CIYAM anyone can create 100% generated C++ web applications in literally minutes.

GPG Public Key | 1ciyam3htJit1feGa26p2wQ4aw6KFTejU
Uniqueorn
Full Member
***
Offline Offline

Activity: 182
Merit: 100

NXT.org


View Profile
March 06, 2014, 04:45:34 PM
 #41228

Difficulty defines bias toward bigger accounts. Set it lower and 10M account will forge 1.1% of all blocks. Set it higher and the account will forge only 1.05%.

So if we limited the forging power of a single account to x then presumably the "difficulty" would become practically irrelevant.



couldn't the account just spread the NXT over more accounts and open more clients to forge?
CIYAM
Legendary
*
Offline Offline

Activity: 1890
Merit: 1028


Ian Knowles - CIYAM Lead Developer


View Profile WWW
March 06, 2014, 04:46:29 PM
 #41229

couldn't the account just spread the NXT over more accounts and open more clients to forge?

Am only referring to the "difficulty" question (not overall power to forge - they can divide up their NXT into multiple accounts right now).

With CIYAM anyone can create 100% generated C++ web applications in literally minutes.

GPG Public Key | 1ciyam3htJit1feGa26p2wQ4aw6KFTejU
Come-from-Beyond
Legendary
*
Offline Offline

Activity: 2142
Merit: 1009

Newbie


View Profile
March 06, 2014, 04:53:32 PM
 #41230

So if we limited the forging power of a single account to x then presumably the "difficulty" would become practically irrelevant.

BCNext intentionally used an algo that creates a small bias, otherwise he would use plain lottery for forging...
EmoneyRu
Hero Member
*****
Offline Offline

Activity: 600
Merit: 500

Nxt-kit developer


View Profile
March 06, 2014, 05:17:35 PM
 #41231

BCNext I intentionally used an algo that creates a small bias, otherwise he I would use plain lottery for forging...

Fixed Wink

antanst
Sr. Member
****
Offline Offline

Activity: 294
Merit: 260


View Profile
March 06, 2014, 05:27:45 PM
 #41232


oh, please:


import numpy as np

import sys
import string
 

def main():
    selChars = string.ascii_letters+ string.digits
    print( selChars)
    numPws=50
    pwLen=80
    
    for pwNum in range(numPws):
        pwDigs=np.random.randint(0,62,pwLen)
        pw=''
        for dig in pwDigs:
            pw += selChars[dig]
        print(pw)

if __name__=='__main__':
    main()


Is there anything special about numpy's random generation? Why not just

Code:
password=''.join([chr(random.choice(range(33,127))) for i in range(64)])

?

Edit: You can also use os.urandom which is supposedly better since it uses the OS' native generator (/dev/urandom on Linux)

bidji29
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250


View Profile
March 06, 2014, 05:37:25 PM
 #41233

Jesse James Aka DoctorEvil on the nextcoin forum (the one who cracked the genesis account passphrase) agreed to do some audit on the Crypto/Curve25519 code.

https://bitcointalk.org/index.php?topic=345619.msg5119097#msg5119097

He said it mi-february. Any news?

http://www.freebieservers.com/  100% FREE GAME SERVERS
marcus03
Full Member
***
Offline Offline

Activity: 224
Merit: 100


View Profile
March 06, 2014, 05:41:04 PM
 #41234

Here is version 2.2 of my Windows/Mac OSX NXT client "NXT Solaris".


Changelog
-Mac OSX version added (source is included in the Windows downloads)
-GUI Performance improvements
-Changed the default testnet address to "http://tn01.nxtsolaris.info:6876/"
-The JCL is no longer needed to compile the source code
-Fixed a bug that prevented sending NXT to accounts without a public key in the BC
-Fixed Bter market data retrieval
-Fixed "secret maps to expected account number" check for secrets with characters beyond ascii
-Added checks for enough funds before broadcasting transactions


Download
64-bit Windows Version: NXTSolaris-v2.2-Win64bit.zip (36.3 MB) – Download here
SHA256 checksum for NXTSolaris-v2.2-Win64bit.zip: BCDC7C27755A138E44AE51FB3F842BB8E12FAC6AF3117F44BB99B9B01B581F95

32-bit Windows Version: NXTSolaris-v2.2-Win32bit.zip (34.3 MB) – Download here
SHA256 checksum for NXTSolaris-v2.2-Win32bit.zip: 0F6851CE16411756EB5ED9ADFBD1AF730CEC0B68D8566660D8A8257C0DF3F7B1

32-bit Mac OSX Version: NXTSolaris-v2.2-OSX32bit.zip (9.5 MB) – Download here
SHA256 checksum for NXTSolaris-v2.2-OSX32bit.zip: 76B416EB3783410E33AC14353501F9FC735863CE725205AE0DF78C1E678F76BD


For screenshots and everything else please visit: http://nxtsolaris.wordpress.com/


Installation
Simply unzip the archive and run the NXTSolarisStarter.exe file.

The current version 2.2 is compatible with the previous versions 2.1.

Roadmap
1.) Move current version of my code to XE5 and release closed source 32-bit and 64-bit versions for Windows. [DONE]
2.) Refactor code to a MVC architecture, so that I can create separate GUIs while using the same version of the business logic code. [DONE]
3.) Create new GUIs for Windows and OS X using the same business logic, but based on the cross-platform Firemonkey libraries. [DONE]
4.) Release Windows version (32 and 64 bit) based on FireMonkey. [DONE]
5.) Implement new features from the TODO list [DONE]
6.) Release source-code for FireMonkey Windows version (February 16th, 2014 latest) [DONE]
7.) Implement new features from the TODO list
8.) OSX compatibility changes
9.) Release OSX version based on FireMonkey.
10.) Release source code for FireMonkey OSX version.


I've reached the end of my roadmap! :-)


TODO list
-Arbitrary message encryption
-Offer a simple and advanced GUI, with the simple GUI targeted at new users



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
l8orre
Legendary
*
Offline Offline

Activity: 1166
Merit: 1008


View Profile
March 06, 2014, 05:41:47 PM
 #41235


oh, please:


import numpy as np

import sys
import string
 

def main():
    selChars = string.ascii_letters+ string.digits
    print( selChars)
    numPws=50
    pwLen=80
    
    for pwNum in range(numPws):
        pwDigs=np.random.randint(0,62,pwLen)
        pw=''
        for dig in pwDigs:
            pw += selChars[dig]
        print(pw)

if __name__=='__main__':
    main()


Is there anything special about numpy's random generation? Why not just

Code:
password=''.join([chr(random.choice(range(33,127))) for i in range(64)])

?

Edit: You can also use os.urandom which is supposedly better since it uses the OS' native generator (/dev/urandom on Linux)

no, nothing special about that. just had it sitting there in the script .
Uniqueorn
Full Member
***
Offline Offline

Activity: 182
Merit: 100

NXT.org


View Profile
March 06, 2014, 05:52:10 PM
 #41236

CFB, are you the only one communicating with BCNext? Who will be in touch with him when you depart in 3 1/2 weeks?

He had left the day before Nxt source code became public. Went for good to work on other things. I'll get 3rd part of the plan in April but I can't contact him anymore.

somebody in the dgex forum said they talk to bcnext frequently, maybe they could help you out?

should we hallmark the testnet nodes or just leave them non hallmarked?


You may be referring to me saying that BCNext told us that NXT is a experiment for him and that he has abandoned the project.
I haven't seen anyone talk about talking to BCNext there.
I got to ask some question through proxy (CfB) to him and he answered, but as far as I know noone else is talking to him
Come-from-Beyond
Legendary
*
Offline Offline

Activity: 2142
Merit: 1009

Newbie


View Profile
March 06, 2014, 05:53:33 PM
 #41237

somebody in the dgex forum said they talk to bcnext frequently, maybe they could help you out?

Maybe.
Come-from-Beyond
Legendary
*
Offline Offline

Activity: 2142
Merit: 1009

Newbie


View Profile
March 06, 2014, 05:55:47 PM
 #41238

From http://mag.newsweek.com/2014/03/14/bitcoin-satoshi-nakamoto.html:

Quote
"Everyone who looked at his code has pretty much concluded it was a single person," says Andresen. "We have rewritten roughly 70 percent of the code since inception. It wasn't written with nice interfaces. It was like one big hairball. It was incredibly tight and well-written at the lower level but where functions came together it could be pretty messy."

BCNext followed Satoshi even in this...
Uniqueorn
Full Member
***
Offline Offline

Activity: 182
Merit: 100

NXT.org


View Profile
March 06, 2014, 05:58:02 PM
 #41239

From http://mag.newsweek.com/2014/03/14/bitcoin-satoshi-nakamoto.html:

Quote
"Everyone who looked at his code has pretty much concluded it was a single person," says Andresen. "We have rewritten roughly 70 percent of the code since inception. It wasn't written with nice interfaces. It was like one big hairball. It was incredibly tight and well-written at the lower level but where functions came together it could be pretty messy."

BCNext followed Satoshi even in this...

My theory is that Satoshi simply had this idea and then had to learn how to code, not the other way around.
I think the same goes for BCNext.
mcjavar
Hero Member
*****
Offline Offline

Activity: 784
Merit: 500


View Profile
March 06, 2014, 06:33:22 PM
 #41240

Jesse James Aka DoctorEvil on the nextcoin forum (the one who cracked the genesis account passphrase) agreed to do some audit on the Crypto/Curve25519 code.

https://bitcointalk.org/index.php?topic=345619.msg5119097#msg5119097

He said it mi-february. Any news?

Could you please follow this up?
Pages: « 1 ... 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 [2062] 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 ... 2557 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!