elective-stereophonic
elective-stereophonic
NRS v1.7.0e
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Nxt Client: Nxt 1.11.15

Pages: 1 [2] 3  All

Author Topic: NRS v1.7.0e  (Read 15000 times)

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +439/-42
  • Offline Offline
  • Posts: 1792
    • View Profile
Re: NRS v1.7.0e
« Reply #20 on: November 30, 2015, 12:19:47 pm »

1. Just to be sure, is it OK to run public node and local note with 1.7.0.e on mainnet?
2. Are there some plans for coin shuffling infographics  for not very tech savy users?

1. Yes, but bare in mind that this is essentially a beta version. The new features are already enabled on testnet and will become enabled on mainnet on block 621000.
2. If someone would like to create one I'll be glad to assist.
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +439/-42
  • Offline Offline
  • Posts: 1792
    • View Profile
Re: NRS v1.7.0e
« Reply #21 on: November 30, 2015, 12:25:58 pm »

Thank!

Question: Jean-Luc wants higher fees to prevent spam, but why costs a singleton asset only 1 NXT to create? I bet that sqatters will register a lot of names after the release, such as happened with the MS, although they are not unique. From user experience point-of-view it will look like Nxt is spammed again.

Assets (unlike currencies and aliases) do not enforce a unique name, you can allocate all the common asset names but this won't prevent anyone else from using the same name.
Asset issuers should always promote the asset id and not the asset name which should only be used for reference.
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

petko

  • Jr. Member
  • **
  • Karma: +24/-0
  • Offline Offline
  • Posts: 98
    • View Profile
    • My blog
Re: NRS v1.7.0e
« Reply #22 on: November 30, 2015, 12:40:33 pm »

Why limit creation of aliases to 1 per block? I know they are not used much, but I don't see a reason for it?

It's a part of the forgers spam prevention - https://nxtforum.org/general/preventing-spam-by-forgers/msg196405/#msg196405
Logged

CryptKeeper

  • Hero Member
  • *****
  • Karma: +78/-5
  • Offline Offline
  • Posts: 1235
    • View Profile
Re: NRS v1.7.0e
« Reply #23 on: November 30, 2015, 02:54:45 pm »

If I want to do a tx from a "controlled" account, I have to select a finish block height which is within the account control range.
There is even a nice error message if you don't enter the correct values, but it would be better if you had a valid default to start with and maybe a slider with which you can only go as far as the account control allows to. Please have a look at the hardcopy and you will understand what I mean:



Current block height is 483180 which isn't valid and neither is the default value in the input field of 490180. The "+" and "-" buttons are useless here because they work in intervals of 500.

This is not an error, but it lacks user friendliness and can be improved.
Logged
Follow me on twitter for the latest news on bitcoin and altcoins!
Vanity Accounts Sale :-)

BTCDDev

  • Full Member
  • ***
  • Karma: +20/-4
  • Offline Offline
  • Posts: 148
    • View Profile
Re: NRS v1.7.0e
« Reply #24 on: November 30, 2015, 03:23:41 pm »

Code: [Select]
2015-11-30 10:21:40 INFO: nxt.dbDefaultLockTimeout = "60"
2015-11-30 10:21:40 FINE: Database jdbc url set to jdbc:h2:nxt_db/nxt;DB_CLOSE_ON_EXIT=FALSE;MVCC=TRUE;CACHE_SIZE=262144 username sa
2015-11-30 10:21:53 SEVERE: org.h2.jdbc.JdbcSQLException: General error: "java.lang.RuntimeException: page[22] data leaf table:387 T387 entries:8 parent:293685 keys:[1730203, 1730204, 1730205, 1730206, 1730207, 1730208, 1730209, 1730210] offsets:[1849, 1623, 1422, 1197, 972, 747, 420, 194] parent 293685 expected 1409519" [50000-176]
java.lang.RuntimeException: org.h2.jdbc.JdbcSQLException: General error: "java.lang.RuntimeException: page[22] data leaf table:387 T387 entries:8 parent:293685 keys:[1730203, 1730204, 1730205, 1730206, 1730207, 1730208, 1730209, 1730210] offsets:[1849, 1623, 1422, 1197, 972, 747, 420, 194] parent 293685 expected 1409519" [50000-176]
at nxt.db.a.a(Unknown Source)
at nxt.ea.a(Unknown Source)
at nxt.ez.<clinit>(Unknown Source)
at nxt.Nxt.e(Unknown Source)
at nxt.Nxt.main(Unknown Source)
Caused by: org.h2.jdbc.JdbcSQLException: General error: "java.lang.RuntimeException: page[22] data leaf table:387 T387 entries:8 parent:293685 keys:[1730203, 1730204, 1730205, 1730206, 1730207, 1730208, 1730209, 1730210] offsets:[1849, 1623, 1422, 1197, 972, 747, 420, 194] parent 293685 expected 1409519" [50000-176]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:344)
at org.h2.message.DbException.get(DbException.java:167)
at org.h2.message.DbException.convert(DbException.java:294)
at org.h2.engine.Database.openDatabase(Database.java:291)
at org.h2.engine.Database.<init>(Database.java:254)
at org.h2.engine.Engine.openSession(Engine.java:57)
at org.h2.engine.Engine.openSession(Engine.java:164)
at org.h2.engine.Engine.createSessionAndValidate(Engine.java:142)
at org.h2.engine.Engine.createSession(Engine.java:125)
at org.h2.engine.Engine.createSession(Engine.java:27)
at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:331)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:107)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:91)
at org.h2.Driver.connect(Driver.java:74)
at org.h2.jdbcx.JdbcDataSource.getJdbcConnection(JdbcDataSource.java:191)
at org.h2.jdbcx.JdbcDataSource.getXAConnection(JdbcDataSource.java:354)
at org.h2.jdbcx.JdbcDataSource.getPooledConnection(JdbcDataSource.java:386)
at org.h2.jdbcx.JdbcConnectionPool.getConnectionNow(JdbcConnectionPool.java:228)
at org.h2.jdbcx.JdbcConnectionPool.getConnection(JdbcConnectionPool.java:200)
... 5 more
Caused by: java.lang.RuntimeException: page[22] data leaf table:387 T387 entries:8 parent:293685 keys:[1730203, 1730204, 1730205, 1730206, 1730207, 1730208, 1730209, 1730210] offsets:[1849, 1623, 1422, 1197, 972, 747, 420, 194] parent 293685 expected 1409519
at org.h2.message.DbException.throwInternalError(DbException.java:241)
at org.h2.index.PageDataIndex.getPage(PageDataIndex.java:247)
at org.h2.index.PageDataNode.getLastKey(PageDataNode.java:215)
at org.h2.index.PageDataNode.getLastKey(PageDataNode.java:215)
at org.h2.index.PageDataNode.getLastKey(PageDataNode.java:215)
at org.h2.index.PageDataIndex.<init>(PageDataIndex.java:88)
at org.h2.table.RegularTable.<init>(RegularTable.java:84)
at org.h2.store.PageStore.addMeta(PageStore.java:1693)
at org.h2.store.PageStore.readMetaData(PageStore.java:1624)
at org.h2.store.PageStore.recover(PageStore.java:1406)
at org.h2.store.PageStore.openExisting(PageStore.java:368)
at org.h2.store.PageStore.open(PageStore.java:289)
at org.h2.engine.Database.getPageStore(Database.java:2366)
at org.h2.engine.Database.open(Database.java:657)
at org.h2.engine.Database.openDatabase(Database.java:260)
... 20 more
2015-11-30 10:21:53 INFO: Shutting down...
2015-11-30 10:21:53 INFO: nxt.adminPassword not defined

Logged

TwinWinNerD

  • Hero Member
  • *****
  • Karma: +222/-116
  • Offline Offline
  • Posts: 2012
  • CEO BitPanda.com
    • View Profile
Re: NRS v1.7.0e
« Reply #25 on: November 30, 2015, 04:32:22 pm »

Thank!

Question: Jean-Luc wants higher fees to prevent spam, but why costs a singleton asset only 1 NXT to create? I bet that sqatters will register a lot of names after the release, such as happened with the MS, although they are not unique. From user experience point-of-view it will look like Nxt is spammed again.

Where does it say that singelton asset names are unique?

edit: oh ryker already ellaborated.
« Last Edit: November 30, 2015, 04:37:55 pm by TwinWinNerD »
Logged

petko

  • Jr. Member
  • **
  • Karma: +24/-0
  • Offline Offline
  • Posts: 98
    • View Profile
    • My blog
Re: NRS v1.7.0e
« Reply #26 on: November 30, 2015, 04:45:15 pm »

This is not an error, but it lacks user friendliness and can be improved.

Indeed! I'll think how to improve it in the next version, maybe I'll clamp the default value and the values that can be set with the (+) and (-) buttons
Logged

lurker10

  • Hero Member
  • *****
  • Karma: +168/-33
  • Offline Offline
  • Posts: 1334
    • View Profile
Re: NRS v1.7.0e
« Reply #27 on: November 30, 2015, 05:16:20 pm »

Code: [Select]
Cannot check shuffler status. Incorrect administrator password. (the specified password does not match nxt.adminPassword)
Code: [Select]
Incorrect administrator password. (the specified password does not match nxt.adminPassword)
I have set nxt.adminPassword in the properties file, is there something else I missed?
Logged
Run a node - win a prize! "Lucky node" project jar: NXT-8F28-EDVE-LPPX-HY4E7

Riker

  • Core Dev
  • Hero Member
  • *****
  • Karma: +439/-42
  • Offline Offline
  • Posts: 1792
    • View Profile
Re: NRS v1.7.0e
« Reply #28 on: November 30, 2015, 05:29:21 pm »

Code: [Select]
Cannot check shuffler status. Incorrect administrator password. (the specified password does not match nxt.adminPassword)
Code: [Select]
Incorrect administrator password. (the specified password does not match nxt.adminPassword)
I have set nxt.adminPassword in the properties file, is there something else I missed?
You need to also set the admin password in the wallet settings under the cog wheel
Logged
NXT Core Dev
Account: NXT-HBFW-X8TE-WXPW-DZFAG
Public Key: D8311651 Key fingerprint: 0560 443B 035C EE08 0EC0  D2DD 275E 94A7 D831 1651

CryptKeeper

  • Hero Member
  • *****
  • Karma: +78/-5
  • Offline Offline
  • Posts: 1235
    • View Profile
Re: NRS v1.7.0e
« Reply #29 on: November 30, 2015, 05:52:31 pm »

This is not an error, but it lacks user friendliness and can be improved.

Indeed! I'll think how to improve it in the next version, maybe I'll clamp the default value and the values that can be set with the (+) and (-) buttons

Thanks. Best default value for finish height would be (current block + account control range) IMHO.
Logged
Follow me on twitter for the latest news on bitcoin and altcoins!
Vanity Accounts Sale :-)

BTCDDev

  • Full Member
  • ***
  • Karma: +20/-4
  • Offline Offline
  • Posts: 148
    • View Profile
Re: NRS v1.7.0e
« Reply #30 on: November 30, 2015, 06:18:45 pm »

Mine immediately shuts down.
Logged

qq2536007339

  • Hero Member
  • *****
  • Karma: +42/-9
  • Offline Offline
  • Posts: 514
    • View Profile
Re: NRS v1.7.0e
« Reply #31 on: December 01, 2015, 07:15:25 am »

After update,testnet stuck on block 483001,and I'm not alone.
https://nxtforum.org/testnet/testnet-not-working/msg202308/?topicseen#msg202308

Seems hardfork in testnet is too early,many nodes didn't update yet.

« Last Edit: December 01, 2015, 07:18:15 am by qq2536007339 »
Logged
你送我阿朵,我是要的。ARDOR-DJ68-PG7W-4JEU-2LU5T

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.7.0e
« Reply #32 on: December 01, 2015, 07:51:16 am »

JL, can you confirm the block time adjustments are the same as the code specified here?
https://nxtforum.org/nxt-improvement-proposals/fixing-the-blocktimes/msg195694/#msg195694

Or does it use the default values in the BaseTargetTest.java that shipped with 1.6.2?

The values right now are as in that post:
Code: [Select]
    private static final long MIN_BASE_TARGET = Constants.INITIAL_BASE_TARGET * 9 / 10;
    private static final long MAX_BASE_TARGET = Constants.isTestnet ? Constants.MAX_BASE_TARGET : Constants.INITIAL_BASE_TARGET * 50;
    private static final int MIN_BLOCKTIME_LIMIT = 53;
    private static final int MAX_BLOCKTIME_LIMIT = 67;
    private static final int GAMMA = 64;
    private static final int SMA_N = 3;
    private static final int FREQUENCY = 2;

At the time I settled on those values because they seemed to give slightly better standard deviation and maximum blocktime, but did those changes on the 1.7 branch only.
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

lurker10

  • Hero Member
  • *****
  • Karma: +168/-33
  • Offline Offline
  • Posts: 1334
    • View Profile
Re: NRS v1.7.0e
« Reply #33 on: December 01, 2015, 04:02:32 pm »

Is it possible to show current/total in the Participant count? It saves a click on the shuffling to check status.
Logged
Run a node - win a prize! "Lucky node" project jar: NXT-8F28-EDVE-LPPX-HY4E7

stdset

  • Jr. Member
  • **
  • Karma: +14/-1
  • Offline Offline
  • Posts: 86
    • View Profile
Re: NRS v1.7.0e
« Reply #34 on: December 01, 2015, 08:07:04 pm »

Great work. This release is probaly second only to the AE release. Or maybe it's even the greatest NXT improvement ever.
I hope to see apps applying power of phased transactions to real world use cases. That's what will drive NXT market cap to the Moon.
Logged

Eveready

  • Jr. Member
  • **
  • Karma: +4/-0
  • Offline Offline
  • Posts: 23
    • View Profile
Re: NRS v1.7.0e
« Reply #35 on: December 02, 2015, 12:50:32 am »

Just tested out a cool use case - set up a mandatory approval account with self as the approver. This way you get to double confirm your transactions (an indirect undo function), but it'll cost you 2+1 NXT for a simple send ;D
Logged

CryptKeeper

  • Hero Member
  • *****
  • Karma: +78/-5
  • Offline Offline
  • Posts: 1235
    • View Profile
Re: NRS v1.7.0e
« Reply #36 on: December 02, 2015, 07:43:14 am »

Just tested out a cool use case - set up a mandatory approval account with self as the approver. This way you get to double confirm your transactions (an indirect undo function), but it'll cost you 2+1 NXT for a simple send ;D

Do you mean "self" as the same account? I've tested with another account I control and that works fine (though gui could need to be polished in terms of usability). It's real multi-sig.

IMHO 3 NXT is not much if you could secure a substantial amount!
Logged
Follow me on twitter for the latest news on bitcoin and altcoins!
Vanity Accounts Sale :-)

Eveready

  • Jr. Member
  • **
  • Karma: +4/-0
  • Offline Offline
  • Posts: 23
    • View Profile
Re: NRS v1.7.0e
« Reply #37 on: December 02, 2015, 08:03:55 am »

Just tested out a cool use case - set up a mandatory approval account with self as the approver. This way you get to double confirm your transactions (an indirect undo function), but it'll cost you 2+1 NXT for a simple send ;D

Do you mean "self" as the same account? I've tested with another account I control and that works fine (though gui could need to be polished in terms of usability). It's real multi-sig.

IMHO 3 NXT is not much if you could secure a substantial amount!

Yes. Same account. It works bcos approving a transaction (Approval Request) is not covered by the Mandatory Approval status, even when approving for other accounts (ie if your account has mandatory approval status, you can still approve other users' approval requests without requiring your whitelisted accounts approving your approval). So if ppl are paranoid about doing a fat finger send from a large account, or are asking for an Undo feature,  this blockchain-based double confirmation account might do the trick.
Logged

lurker10

  • Hero Member
  • *****
  • Karma: +168/-33
  • Offline Offline
  • Posts: 1334
    • View Profile
Re: NRS v1.7.0e
« Reply #38 on: December 02, 2015, 10:15:09 am »

I was able to submit a shuffling registration for the asset I don't have, is this correct behavior? My account is not in the registration list, only browser message popped up and was logged that shuffler was started, did I get in or not after all?
« Last Edit: December 02, 2015, 10:18:01 am by lurker10 »
Logged
Run a node - win a prize! "Lucky node" project jar: NXT-8F28-EDVE-LPPX-HY4E7

NxtSwe

  • Hero Member
  • *****
  • Karma: +124/-9
  • Offline Offline
  • Posts: 657
    • View Profile
Re: NRS v1.7.0e
« Reply #39 on: December 02, 2015, 03:22:15 pm »

A question about the getHoldingShufflings api function.
Is it expected to return empty array if you don't specify any holding?
Example: http://localhost:6876/nxt?requestType=getHoldingShufflings&includeFinished=true

While if I add on a holding parameter, I get result back.
Example: http://localhost:6876/nxt?requestType=getHoldingShufflings&holding=9836948456938609454&includeFinished=true

This indicates that the holding parameter is required, yet I get no error message saying it is required, just an empty result back.
It does not seem to be intentional, as it is not the way the api works in other cases.
Logged
Check out the NxtLib, the .NET Framework API for the Nxt platform.
Pages: 1 [2] 3  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly