elective-stereophonic
elective-stereophonic
Show Posts - jnsptrsn singapore
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.2

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - jnsptrsn

Pages: [1] 2 3 4
1
Nxt Helpdesk / Re: nxt and Ardor on same VPS?
« on: January 02, 2018, 07:59:13 pm »
Yes, it is possible.

2
Nxt General Discussion / Re: Price speculation
« on: December 30, 2017, 11:43:40 am »
well i had two wallets and the same happnd on both in the one i had to had small amount of Ardors well i have only the 1/3 of the Amount i have ot have.

The other account, this morning i had the Ardors and Ignis from the airdrop im cheking now again same Half of the Ardors and Half of the Ignis gone without trace without any transaction?

I guess you are using Ardor testnet, right? Try the production version 2.0.9.

3
Ardor Software Releases / Re: Ardor v2.0.8e
« on: December 26, 2017, 02:41:27 pm »

4
Ardor Software Releases / jnsptrsn
« on: December 26, 2017, 02:28:24 pm »
The new testnet genesis block is based on a snapshot of the Nxt blockchain at
height 1631000. Forging on testnet is set to start at 14:00 UTC, Dec 26.

I might be wrong, but it's half the amount of IGNIS and Ardor in my testnet account compared to what I expected.

Let's say I had 100 NXT and 100 ARDR at block 1631000 on NXT production net on my account NXT-ABC. When I check account ARDOR-ABC on testnet, I have:

50 Ardor
25 Ignis

Shouldn't it be 100 Ardor and 50 Ignis?

5
Nxt General Discussion / Re: Shuffling party time (ARDR edition)
« on: December 15, 2017, 03:00:58 pm »
Bump.


Don't forget to shuffle your ARDR before the snapshot on Dec 28!

6
Nxt General Discussion / Re: Shuffling questions
« on: December 12, 2017, 10:46:25 pm »
It is my understanding that there is no need to make an outgoing transaction from the recipient account to secure it when a shuffling is successfully finished, due to the fact that the public keys of the recipients are announced to the network during the shuffling process. Is that correct?

7
Nxt General Discussion / Re: Need more testnet nodes
« on: September 11, 2016, 09:06:41 pm »
I'm starting up one with open api and ssl.

8
Nxt General Discussion / Re: Lottery
« on: August 13, 2016, 11:43:30 am »
I think you should use the same method as NXTBubble/ToTheMoon and other projects like that: a hash-chain that is used in reverse to get a pseudo-random seed for each game. The seed for the first hash in the chain could be a NXT or Bitcoin block hash at some height in the future from now.

Much of the NxtBubble info is removed from this forum, but here is a start: https://nxtforum.org/nxtbubble-com/nxtbubble-verifier/


9
Official Nxt Releases / Re: NRS v1.10.1
« on: August 10, 2016, 10:09:54 pm »
It's time you refresh your copy of the key ;-)

Ahh, so it's that time of the year :)
Thanks!

10
Official Nxt Releases / Re: NRS v1.10.1
« on: August 10, 2016, 04:10:13 pm »
Thanks,

seems like it's time to renew your key:

Code: [Select]
pub   4096R/E1E4240C 2015-07-29 [expired: 2016-07-28]
uid       [ expired] Jean-Luc Picard (Lead Developer of The Nxt Generation) <jlp@secure.mailbox.org>
uid       [ expired] Jean-Luc Picard (Lead Developer of The Nxt Generation) <jlp@mailbox.org>
uid       [ expired] Jean-Luc Picard (Lead Developer of The Nxt Generation) <jlp666@yandex.ru>

11
Thanks for the NSC. But I don't understand how I can sell them. I want to publish an exchange offer, but why do I need to buy too? I don't want that, but if I leave the fields blank the order is not good.  :-\

No, you don't have to. When listing your MS currencies in your wallet, click on the "Exchange" button (not the "Offer" button). There you can see current sell/buy orders and place your own.

12
Official Nxt Releases / Re: NRS v1.10.0e
« on: July 31, 2016, 02:18:42 pm »
Works like a charm.

13
Official Nxt Releases / Re: NRS v1.10.0e
« on: July 31, 2016, 12:57:42 pm »
The js client does not blindly sign the tx, it verifies that the unsigned bytes from the node are correct first.

Great, thank you. Why does it need the node to create the unsigned bytes then?

Edit: Ok, I can see benefits of the nodes creating it. I'm happy with the answer :)

14
Official Nxt Releases / Re: NRS v1.10.0e
« on: July 31, 2016, 12:49:09 pm »
To my understanding, the JS client have no functionality to parse or create transaction bytes itself. So when it initiates a transaction, the unsigned transaction bytes are created by the node and signed locally by the JS client. Right?

I think this is a major security issue which is easy to exploit. A malicious node could easily create evil transaction bytes that the JS client blindly will sign. It does not need to steel your passphrase to steel your NXT.

15
Now you get bonus coins for:
* hallmarking your node and having weight>0;
* open API
* open API_SSL
* running an archival node

First of all, great initiative!

Then a thought. Should it really be encouraged to run a node with open non-SSL API?

Yes, why not.

Communication with passphrases to nodes is not recommended in any way. Wrap them up local and use broadcastTransaction to submit verified transaction. Also not-SSL nodes can be used to get data from the blockchain. while SSL is always better than not having it. But not required to get data from website

You said it yourself: SSL is always better.

Yes, but not easy for everyone. To encourage we discuss SSL details here: https://nxtforum.org/public-nodes-vpss/method-to-configure-https-for-nxt-public-nodes/

True. Not easy for everyone. I still think it's better to only reward best practice.

16
Trading & Exchanges / Re: Ardor beta release didn't benefit NXT price
« on: July 15, 2016, 04:58:02 pm »
There has not been any release of Ardor. Please check the roadmap here:
https://nxtforum.org/core-development-announcements/announcing-nxt-2-0-roadmap/

Don't confuse the start the snapshot period with any kind of release.

17
Now you get bonus coins for:
* hallmarking your node and having weight>0;
* open API
* open API_SSL
* running an archival node

First of all, great initiative!

Then a thought. Should it really be encouraged to run a node with open non-SSL API?

Yes, why not.

Communication with passphrases to nodes is not recommended in any way. Wrap them up local and use broadcastTransaction to submit verified transaction. Also not-SSL nodes can be used to get data from the blockchain. while SSL is always better than not having it. But not required to get data from website

You said it yourself: SSL is always better.

18
Now you get bonus coins for:
* hallmarking your node and having weight>0;
* open API
* open API_SSL
* running an archival node

First of all, great initiative!

Then a thought. Should it really be encouraged to run a node with open non-SSL API?

19
Nxt Helpdesk / Re: How to find my public key
« on: July 12, 2016, 06:44:50 pm »
It's not a good idea to write your passphrase as part of an URL in your browser. Not if you are keen on keeping your passphrase a secret. It will be stored in your browsers cache, and if you are using a modern browser it's likely that it will be sent to the cloud.

Better to click on the Account info

Thanks a good point, I was wondering about this too. But didn't find another way. Actually account info doesn't show the public key for me (just: "/"). So, it's not just that my public key is not published but somehow my account doesn't recognize a public key altogether. I'm wondering if in this case the following suggestion helps:

You need to login using your passphrase. I should have mentioned that.

Ah ok, I was not aware about the option to login with passphrase. It makes sense, thanks a lot.

The possibility is not obvious :) I edited my last post on how to do it.

20
Nxt Helpdesk / Re: How to find my public key
« on: July 12, 2016, 06:34:16 pm »
It's not a good idea to write your passphrase as part of an URL in your browser. Not if you are keen on keeping your passphrase a secret. It will be stored in your browsers cache, and if you are using a modern browser it's likely that it will be sent to the cloud.

Better to click on the Account info

Thanks a good point, I was wondering about this too. But didn't find another way. Actually account info doesn't show the public key for me (just: "/"). So, it's not just that my public key is not published but somehow my account doesn't recognize a public key altogether. I'm wondering if in this case the following suggestion helps:

You need to login using your passphrase. I should have mentioned that.

Click here:


To get here:

Pages: [1] 2 3 4
elective-stereophonic
elective-stereophonic
assembly
assembly