Can someone explain me how to get rid of the local time issues (I'm on 0.7.6, but this happened also with previous versions)? For instance, I get the following message in the console:
[2014-02-19 19:47:27.452] DEBUG: Will pop block 8909105522996058296 at height 70422
and then in the NRS client I see this as an orphaned block with time 20:47:11 (i.e., one hour ahead of my true local time, which was really 19:47). My system clock is synchronized with NTP (Brasil/East), I'm using Mageia linux (version 3).
set your system to UTC then NTP sync with UTC, then change any DST/TZ settings to correct the clock. Just dont manually adjust the clock to correct for DST/TZ. Barring that, not sure what issues you are having When I change it to UTC, it displays incorrect time (+3h from here). Don't understand, how do I do the things you described in the drakclock...  That 1st step is to set pc timezone entry setting to utc, then sync ntp, then setentries for dst and tz as needed. That's what I see when trying to adjust the clock in Mageia ("Fuso horário" is timezone in Portuguese):  There are no entries for dst & tz, it seems. Ugh sorry dude, maybe someone else can help. theres got to be a way in linux to fix that |
|
|
|
Can someone explain me how to get rid of the local time issues (I'm on 0.7.6, but this happened also with previous versions)? For instance, I get the following message in the console:
[2014-02-19 19:47:27.452] DEBUG: Will pop block 8909105522996058296 at height 70422
and then in the NRS client I see this as an orphaned block with time 20:47:11 (i.e., one hour ahead of my true local time, which was really 19:47). My system clock is synchronized with NTP (Brasil/East), I'm using Mageia linux (version 3).
set your system to UTC then NTP sync with UTC, then change any DST/TZ settings to correct the clock. Just dont manually adjust the clock to correct for DST/TZ. Barring that, not sure what issues you are having When I change it to UTC, it displays incorrect time (+3h from here). Don't understand, how do I do the things you described in the drakclock... That 1st step is to set pc timezone entry setting to utc, then sync ntp, then setentries for dst and tz as needed. |
|
|
|
Can someone explain me how to get rid of the local time issues (I'm on 0.7.6, but this happened also with previous versions)? For instance, I get the following message in the console:
[2014-02-19 19:47:27.452] DEBUG: Will pop block 8909105522996058296 at height 70422
and then in the NRS client I see this as an orphaned block with time 20:47:11 (i.e., one hour ahead of my true local time, which was really 19:47). My system clock is synchronized with NTP (Brasil/East), I'm using Mageia linux (version 3).
set your system to UTC then NTP sync with UTC, then change any DST/TZ settings to correct the clock. Just dont manually adjust the clock to correct for DST/TZ. Barring that, not sure what issues you are having |
|
|
|
|
right, we do get that, but ideally, the goal is a trustless environment. Browser/JS signing and sending/receiving data with public servers allows this, without forcing a local blockchain sync, so this is our end game goal
|
|
|
|
Yes well that's what my wallet will do (it will be downloadable, not just on the web)
very cool. A system that does not have to maintain complete blockchain and can just send transactions to public nodes and query for inbound transactions will be tremendous for NXT and its adoption |
|
|
|
Best case is to wait for a javascript client that signs outbound transactions and polls public nodes for inbound transactions. We REALLY need this, if this comes out....price will skyrocket.
Umm isn't that what my client does ? http://nxtra.org/nxt-client (ok, it doesn't yet sign outbound transactions, but it's on my todo list :-)) right, what I mean is the ability to have a wallet where your passphrase is kept completely local. a system with no trust. |
|
|
|
Don't trust online wallets.
THIS THIS THIS. you can never fully trust online wallets! EVEN IF they have SSL certs! By trusting an online wallet you are trusting anyone who has access to the server. Do you know how many people that is? If its a VPS its even worse! Best case is to wait for a javascript client that signs outbound transactions and polls public nodes for inbound transactions. We REALLY need this, if this comes out....price will skyrocket. |
|
|
|
please add me back to the one in Nevada. And if no one else wants to step up to assist rickyjames in Austin, I will for that one as well |
|
|
|
I already have and they told me they wanted us to pay to integrate it into his system. If we would do that then he would add it. wow. Why do exchanges do that these days? I guess if they don't want our sweet trading fees, so be it for now! Atomic-trade looks like they run a tight ship. With the GoxStampBTCe debacle, a United States based AML and KYC compliant crypto exchange would provide a great avenue for Americans to buy NXT almost directly from their bank accounts. At this moment, there are delays at cashintocoins, bit stamp, box, and BTCe. Americans wanting to buy BTC, then NXT have to use localbitcoins.com then https://www.bter.com or dgex.com. Considering the bottleneck in available methods to buy bit coin at this moment, I think investing in assistance to atomic-trade integrating NXT into its exchange would be wise. I don't think this assistance should be viewed as a bribe. Atomic-trade is KYC and AML compliant after all and they would never accept a bribe. Think. One less step for millions of potential nxters in the USA to acquire NXT WITHOUT ever buying and selling BITCOIN. Keep It Simple. I agree, I doubt few would disagree. So we feel them out and see how much "assistance" they need. Ill volunteer as much time as they need for NRS integration into their system. i have tons of free time during day/night |
|
|
|
OK so as far as web browser javascript transaction generation and signing goes, does it matter where the end client sends their signed transaction to? do they have to send it to a NRS process that has active forgers, or can they just send it to any NRS system with a synced blockchain? Im asking because Im considering opening up API for all the 24 VPSs I manage on nxtcrypto.org and am also considering adding SSL certs for that domain into the Jetty for each server as well.
The node doesn't need to be forging. If you send a transaction to any node, it will broadcast it to others, and eventually a forging node will include it in a block. ok, ill pursue getting SSL running on those VPSs, and opening up API for allowedBotHosts to * and leave allowedUserHosts nulled out to prevent remote forging, unless someone can think of a reason to open that up as well IIRC, each node analyzes the known graph and assumes the longest chain as the correct one.
The same in Nxt. Anon136's video described it as the chain that had the most stake involved in forging the blocks was the 'correct' one, even though there may be a longer chain.  |
|
|
|
what are the planned scopes and responsibilities for the 3 groups? seems to me that tech/infrastructure will overlap quite a bit |
|
|
|
|
OK so as far as web browser javascript transaction generation and signing goes, does it matter where the end client sends their signed transaction to? do they have to send it to a NRS process that has active forgers, or can they just send it to any NRS system with a synced blockchain? Im asking because Im considering opening up API for all the 24 VPSs I manage on nxtcrypto.org and am also considering adding SSL certs for that domain into the Jetty for each server as well.
|
|
|
|
Here goes again: [2014-02-18 15:28:39.676] DEBUG: Failed to accept block 114652587818176816 at he ight 69417 received from vps5.nxtcrypto.org, blacklisting [2014-02-18 15:28:40.722] DEBUG: Failed to accept block 114652587818176816 at he ight 69417 received from vps5.nxtcrypto.org, blacklisting [2014-02-18 15:28:41.772] DEBUG: Failed to accept block 114652587818176816 at he ight 69417 received from vps5.nxtcrypto.org, blacklisting [2014-02-18 15:28:42.820] DEBUG: Failed to accept block 114652587818176816 at he ight 69417 received from vps5.nxtcrypto.org, blacklisting [2014-02-18 15:28:43.892] DEBUG: Failed to accept block 114652587818176816 at he ight 69417 received from vps5.nxtcrypto.org, blacklisting [2014-02-18 15:28:44.942] DEBUG: Failed to accept block 114652587818176816 at he ight 69417 received from vps5.nxtcrypto.org, blacklisting [2014-02-18 15:28:45.993] DEBUG: Failed to accept block 114652587818176816 at he ight 69417 received from vps5.nxtcrypto.org, blacklisting [2014-02-18 15:28:47.042] DEBUG: Failed to accept block 114652587818176816 at he ight 69417 received from vps5.nxtcrypto.org, blacklisting I've downloaded 0.7.5 new (from nxtcrypto) deleted the previous version, started from fresh, blockchain downloaded. After a minute or so the above messages start appearing. Deleted the nxt_db folder, but again after a minute those messages start appearing. I don't think I'm on a fork, because all my transactions show up, even the forged block from the day before yesterday. What's going on? I want to be absolutely sure I don't lose any NXT and I want to do some transactions. Could someone please assist me (in non-technical wording, okay technical is okay, just not programming deep-into-nxt stuff)  Block explorer shows that block at 69418 http://blocks.nxtcrypto.org/nxt/nxt.cgi?action=1000&blk=114652587818176816 and Ive queried vps5.nxtcrypto.org for that block: # ncli getBlock vps5 114652587818176816
baseTarget: 648186177
blockSignature: f1e70a7cfc14191f9e7076c86d6383cfc142d4ba256db1ecb7cf449ade888100d9fd6401529d41a76d4728d22391e485e5a393226ff44b0fa4a5deea5deedb8c
generationSignature: 58faf5d7aec9720f2267b0f4079f0d949c18b1f45a5065331b0492187cdf51ea
generator: 14571285356259793594
height: 69418
nextBlock: 4650020713678921687
numberOfTransactions: 0
payloadHash: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
payloadLength: 0
previousBlock: 7165854537706726184
previousBlockHash: 28632158bc3a726325198d30038354087cfc15ce5fc3ff902157f9f37e0c9ae0
timestamp: 7439343
totalAmount: 0
totalFee: 0
transactions:
version: 2
#
so vps5 agrees with block explorer. do a getBlock API on your client and get us the results: https://localhost:7875/nxt?requestType=getBlock&block=114652587818176816 |
|
|
|
[TEST RELEASE OF NODECOIN MINER]
what happens if more that 1 accounts try to run on the same box? |
|
|
|
dude, the longer you dont author our white paper, the more we will suspect you are BCNext. |
|
|
|
CfB,
Is there a definition of the bytes in a transaction? I am trying to figure out which ones are AM and which ones are not.
I thought maybe doing a getTransaction call would return what type of transaction it is, but it doesnt seem to.
Where can we get a reference on decoding the bytes of a getTransactionBytes API call? And is there anyway to get the bytes for an entire block? Id really like to learn more about the bits/bytes of NXT, can someone point me in the right direction as far as decoding the blockchain? |
|
|
|
Deciding where the decimal goes from the outset, and then sticking with it (FIXED point operations) removes all of the risk of this kind of error.
yes, JLP has already come out and said the conversion to NXT-cents, and to allow for .1 as a fee will be more complex, exactly for the reasons you state. you can see in the code that in some places its just a long/integer and some other places there is a 100L division. He is going to have to standardize before we get the new functionality |
|
|
|
|
and if the community feels like its the way to go, i dont think we'd have any problem at all with migrating www/wiki/info/download/forums .nxtcrypto.org sites to be on .nxt.org at least I would hope that the people involved in those sites would not have a problem.
if thats they way the community wants to go.
|
|
|
|
CfB (or anybody that knows)
What is the best way to invoke API from C?
I just need one example of the right way, eg. is it using curl, if so can you post exact syntax
Thanks
James
Use curl to send a HTTP GET request. Ah, so GET not POST Can you show me exact syntax, especially something that gets it directly into memory? |
|
|
|
|
Show Posts
