Topic: Closed Thread - page 370. (Read 677687 times)
Just letting you know their is a type in the client, says blockchain verified complaite should be complete.
I was in the same situation two days ago. I was selling three stakes, the buyer sent first. The 1 NODE test transaction arrived. The second one few minutes later (1 stake worth) not. After I restarted the client the transaction disappeared. I resent, but that didn't want to show up either, but as it shown on the blockchain explorer, we waited the night. It was alright next day, but I felt uncomfortable as I already got payment for something that I coudn't provide.
NODE has a long way to go, exchange is not even an option at this point.
Therefore, we are in beta testing
Technically, when you create a transaction is held in memory on your PC and then it gets to the network for all its peers are verifying and generating blocks. Only after that it gets to blockchain
You last night did 2 transactions, and everything was ok
Compared to 10 days ago, the network is stable, our plans for the next week to finish all the tests for a stable network. Next we will work on the exchange
I'll resend today as and if it doesn't work again I'll send you back your NXT - no worries 
.
@SillkRoad: So what's with the updating several times a day ? Could you tell me when I can send a tx that will actually go through ?
. @SillkRoad: So what's with the updating several times a day ? Could you tell me when I can send a tx that will actually go through ?
I was in the same situation two days ago. I was selling three stakes, the buyer sent first. The 1 NODE test transaction arrived. The second one few minutes later (1 stake worth) not. After I restarted the client the transaction disappeared. I resent, but that didn't want to show up either, but as it shown on the blockchain explorer, we waited the night. It was alright next day, but I felt uncomfortable as I already got payment for something that I coudn't provide.
NODE has a long way to go, exchange is not even an option at this point.
Last night was the updating of the network and the transaction does not fall within this time
He needs to do a new transaction, as his coins were not synchronized and Departures
We do update several times a day
He needs to do a new transaction, as his coins were not synchronized and Departures
We do update several times a day
Thank you for the answer SillkRoad. I'm fairly certain he will resend but its still a kind of a pickle. Well for all the people asking to be on exchanges,
its pretty obvious NODE is not ready yet for that. Give the devs the time they need to finish this coin.
I'll resend today as and if it doesn't work again I'll send you back your NXT - no worries
. @SillkRoad: So what's with the updating several times a day ? Could you tell me when I can send a tx that will actually go through ?
How does a client get selected for Forging?
Now one of those who is online
So it's random?
Temporary, yes!
How does a client get selected for Forging?
Now one of those who is online
So it's random?
How does a client get selected for Forging?
Now one of those who is online
Last night was the updating of the network and the transaction does not fall within this time
He needs to do a new transaction, as his coins were not synchronized and Departures
We do update several times a day
He needs to do a new transaction, as his coins were not synchronized and Departures
We do update several times a day
Thank you for the answer SillkRoad. I'm fairly certain he will resend but its still a kind of a pickle. Well for all the people asking to be on exchanges,
its pretty obvious NODE is not ready yet for that. Give the devs the time they need to finish this coin.
We finish the main stable network and then expand the functionality
Last night was the updating of the network and the transaction does not fall within this time
He needs to do a new transaction, as his coins were not synchronized and Departures
We do update several times a day
He needs to do a new transaction, as his coins were not synchronized and Departures
We do update several times a day
Thank you for the answer SillkRoad. I'm fairly certain he will resend but its still a kind of a pickle. Well for all the people asking to be on exchanges,
its pretty obvious NODE is not ready yet for that. Give the devs the time they need to finish this coin.
How does a client get selected for Forging?
It looks like people can generate blocks that contain their own txs so they end up getting their own txs fees back? This has to be changed.
Forging is not yet fully configured, we are at this stage, if you are the only one who made the last transaction online and the commission goes back to you, as you have generated block
First I made a trade with a reputable member many hours ago. He said he sent the NODE a long time ago and gave this
tx id 10179771427853359203. The block explorer doesn't let me search by tx id but only by account #. He is offline until tomorrow so I don't know
what his account # is. Obviously I never got the NODE. So I noticed the blocks haven't moved in a long time. So I did a tiny send to test it out.
It never got sent and never showed up in the blocks. So now I'm relieved because my guy probably did send it but NODE is just stuck. So a little later I decide to do more sends only instead of using the 0.5 beta I create a throw away account using the no https webwallet. Now everything I send through the online wallet goes through quickly and reliably.
Not only that but my new throw away account which I do not even remember the passphrase for is also generating my own transactions and everybody else's. So I sign out and make up a new account with an easy to hack passphrase and I send more small amounts. So of course they all go through and I am still the only generator of them. I am the generator of the last 15 or so blocks in a row using different accounts but all using the web wallet. I am simultaneously signed in on the beta wallet with a different account which hasn't generated a single block.
So what is going on? What has happened to my large NODE purchase that most likely was sent but never showed up?
tx id 10179771427853359203. The block explorer doesn't let me search by tx id but only by account #. He is offline until tomorrow so I don't know
what his account # is. Obviously I never got the NODE. So I noticed the blocks haven't moved in a long time. So I did a tiny send to test it out.
It never got sent and never showed up in the blocks. So now I'm relieved because my guy probably did send it but NODE is just stuck. So a little later I decide to do more sends only instead of using the 0.5 beta I create a throw away account using the no https webwallet. Now everything I send through the online wallet goes through quickly and reliably.
Not only that but my new throw away account which I do not even remember the passphrase for is also generating my own transactions and everybody else's. So I sign out and make up a new account with an easy to hack passphrase and I send more small amounts. So of course they all go through and I am still the only generator of them. I am the generator of the last 15 or so blocks in a row using different accounts but all using the web wallet. I am simultaneously signed in on the beta wallet with a different account which hasn't generated a single block.
So what is going on? What has happened to my large NODE purchase that most likely was sent but never showed up?
Last night was the updating of the network and the transaction does not fall within this time
He needs to do a new transaction, as his coins were not synchronized and Departures
We do update several times a day
First I made a trade with a reputable member many hours ago. He said he sent the NODE a long time ago and gave this
tx id 10179771427853359203. The block explorer doesn't let me search by tx id but only by account #. He is offline until tomorrow so I don't know
what his account # is. Obviously I never got the NODE. So I noticed the blocks haven't moved in a long time. So I did a tiny send to test it out.
It never got sent and never showed up in the blocks. So now I'm relieved because my guy probably did send it but NODE is just stuck. So a little later I decide to do more sends only instead of using the 0.5 beta I create a throw away account using the no https webwallet. Now everything I send through the online wallet goes through quickly and reliably.
Not only that but my new throw away account which I do not even remember the passphrase for is also generating my own transactions and everybody else's. So I sign out and make up a new account with an easy to hack passphrase and I send more small amounts. So of course they all go through and I am still the only generator of them. I am the generator of the last 15 or so blocks in a row using different accounts but all using the web wallet. I am simultaneously signed in on the beta wallet with a different account which hasn't generated a single block.
So what is going on? What has happened to my large NODE purchase that most likely was sent but never showed up?
tx id 10179771427853359203. The block explorer doesn't let me search by tx id but only by account #. He is offline until tomorrow so I don't know
what his account # is. Obviously I never got the NODE. So I noticed the blocks haven't moved in a long time. So I did a tiny send to test it out.
It never got sent and never showed up in the blocks. So now I'm relieved because my guy probably did send it but NODE is just stuck. So a little later I decide to do more sends only instead of using the 0.5 beta I create a throw away account using the no https webwallet. Now everything I send through the online wallet goes through quickly and reliably.
Not only that but my new throw away account which I do not even remember the passphrase for is also generating my own transactions and everybody else's. So I sign out and make up a new account with an easy to hack passphrase and I send more small amounts. So of course they all go through and I am still the only generator of them. I am the generator of the last 15 or so blocks in a row using different accounts but all using the web wallet. I am simultaneously signed in on the beta wallet with a different account which hasn't generated a single block.
So what is going on? What has happened to my large NODE purchase that most likely was sent but never showed up?
It looks like people can generate blocks that contain their own txs so they end up getting their own txs fees back? This has to be changed.
Can we please start spreading the word about node on twitter? Also, you need to start pushing this to node.js enthusiasts and developers. It's a huge community and a very good demographic to support us.
Day after day people only search bad things to say about NODE ,devs are very actives on the forum every time reply people spreading FUD ... I hope one day these people stop search this problems in another altcoins and search the problems in this own projects ... 
just my simple think.
just my simple think.
The devs are becoming more active on the thread... does this mean that we are expecting something to happen... hmmm very very suspicious 
1) How do you confirm the transaction
-When Adding transaction peers sends it all when another peer receives a new transaction, and it is valid, it again sends it to all active peers, if the transaction is already with peer and came transaction is valid - it is added confirmation
With this work we want to achieve high speed confirmation, so you can get more than 50 - 100 confirmation in less than 1-3 seconds
If the user Node will pay in the store will receive a quick result as Visa or PayPal
2) How does the verification blocks
- Similar to confirm the transaction
So blocks and txs are spread through the network and every single NODE node (that's a little weird to write
) validates it and if valid spread it further ? If a node receives a tx or block again it is considered a confirmation ?Isn't that susceptible to a sybill attack ? What if I put up many NODE nodes and spread my bogus txs like a maniac ?
I'm sure I'm missing something so I'm just asking because I want to understand
I'd appreciate an answer
Yes, I too was wondering about the technical details relating to this question.
Thanks
If the transaction is valid then there is no problem, you will help the network by contributing your node-power! But If the transaction is invalid, that it will be marked as invalid in every peer that receives it, it just will not work in any client
even if it has already 100.500 confirmations when it will come into the working node.
Each block and the transaction is validated before confirming or adding!
Your nodes will be marked as spamming wrong transaction, and your nodes simply fall into the black lists (it will be implemented later as a security measure)
Node.js technology allows you to handle more than one hundred thousand connections per second
So basically each NODE node holds it's own blockchain and decides wether a transaction is valid on it's own ?
Yes, and NO! All the peers have the same copies of one blockchain and the active peers decide upon the creation of a new block and syncing with the new copy of the blockchain! For this system to work there will be a definite number of peers that will be forever active, and by motivating individuals with forging we will expand the network!
So this is an example of the above mentioned:
Lets say we have 3 peers
2(a & b) of them are active and one (coffee) is not!
Within 2 weeks Peer A & B made 100 trx and constructed 80 blocks! At a given moment of time peer C connects to the network!
As a node it will first sync with other active peers and at the same time verify the correctitude of the blocks
1) How do you confirm the transaction
-When Adding transaction peers sends it all when another peer receives a new transaction, and it is valid, it again sends it to all active peers, if the transaction is already with peer and came transaction is valid - it is added confirmation
With this work we want to achieve high speed confirmation, so you can get more than 50 - 100 confirmation in less than 1-3 seconds
If the user Node will pay in the store will receive a quick result as Visa or PayPal
2) How does the verification blocks
- Similar to confirm the transaction
So blocks and txs are spread through the network and every single NODE node (that's a little weird to write
) validates it and if valid spread it further ? If a node receives a tx or block again it is considered a confirmation ?Isn't that susceptible to a sybill attack ? What if I put up many NODE nodes and spread my bogus txs like a maniac ?
I'm sure I'm missing something so I'm just asking because I want to understand
I'd appreciate an answer
Yes, I too was wondering about the technical details relating to this question.
Thanks
If the transaction is valid then there is no problem, you will help the network by contributing your node-power! But If the transaction is invalid, that it will be marked as invalid in every peer that receives it, it just will not work in any client
even if it has already 100.500 confirmations when it will come into the working node.
Each block and the transaction is validated before confirming or adding!
Your nodes will be marked as spamming wrong transaction, and your nodes simply fall into the black lists (it will be implemented later as a security measure)
Node.js technology allows you to handle more than one hundred thousand connections per second
So basically each NODE node holds it's own blockchain and decides wether a transaction is valid on it's own ?
Every time i start the client it checks all the blocks, will this change in the future or will it always need to check every block? With 690 blocks it takes close to 5 mins before my client can be used because it is checking blocks.
it be later, and now checking goes through json
We will change the algorithm for checking through the transmission of data in bytes
Every time i start the client it checks all the blocks, will this change in the future or will it always need to check every block? With 690 blocks it takes close to 5 mins before my client can be used because it is checking blocks.
1) How do you confirm the transaction
-When Adding transaction peers sends it all when another peer receives a new transaction, and it is valid, it again sends it to all active peers, if the transaction is already with peer and came transaction is valid - it is added confirmation
With this work we want to achieve high speed confirmation, so you can get more than 50 - 100 confirmation in less than 1-3 seconds
If the user Node will pay in the store will receive a quick result as Visa or PayPal
2) How does the verification blocks
- Similar to confirm the transaction
So blocks and txs are spread through the network and every single NODE node (that's a little weird to write
) validates it and if valid spread it further ? If a node receives a tx or block again it is considered a confirmation ?Isn't that susceptible to a sybill attack ? What if I put up many NODE nodes and spread my bogus txs like a maniac ?
I'm sure I'm missing something so I'm just asking because I want to understand
I'd appreciate an answer
Yes, I too was wondering about the technical details relating to this question.
Thanks
If the transaction is valid then there is no problem, you will help the network by contributing your node-power! But If the transaction is invalid, that it will be marked as invalid in every peer that receives it, it just will not work in any client
even if it has already 100.500 confirmations when it will come into the working node.
Each block and the transaction is validated before confirming or adding!
Your nodes will be marked as spamming wrong transaction, and your nodes simply fall into the black lists (it will be implemented later as a security measure)
Node.js technology allows you to handle more than one hundred thousand connections per second
Jump to: