Topic: Closed Thread - page 371. (Read 677687 times)
If there are people running NODE right now try this, move your system time ahead 1 hr, hopefully we can get a few people to to do this to see what happens. Im at work right now so i can't take part, maybe we can organize some tests later on.
im guessing that the wallet has to be closed and re opened manually for the blocks to update as i left mine open and it was stuck on block 665.
i re-opened the wallet and now on 694
i re-opened the wallet and now on 694
Peers sometimes go on updated throughout the day, because of this, you must restart the client
No, the peers are constantly synchronizing with each other! I was referring at client update, as we continuously change something, older versions don't update unless re-started!
Sorry for my broken english
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
i also would like to know
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
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
im guessing that the wallet has to be closed and re opened manually for the blocks to update as i left mine open and it was stuck on block 665.
i re-opened the wallet and now on 694
i re-opened the wallet and now on 694
Peers sometimes go on updated throughout the day, because of this, you must restart the client
No, the peers are constantly synchronizing with each other! I was referring at client update, as we continuously change something, older versions don't update unless re-started!
Sorry for my broken english
im guessing that the wallet has to be closed and re opened manually for the blocks to update as i left mine open and it was stuck on block 665.
i re-opened the wallet and now on 694
i re-opened the wallet and now on 694
Peers sometimes go on updated throughout the day, because of this, you must restart the client
im guessing that the wallet has to be closed and re opened manually for the blocks to update as i left mine open and it was stuck on block 665.
i re-opened the wallet and now on 694
i re-opened the wallet and now on 694
Peers sometimes go on updated throughout the day, because of this, you must restart the client
im guessing that the wallet has to be closed and re opened manually for the blocks to update as i left mine open and it was stuck on block 665.
i re-opened the wallet and now on 694
i re-opened the wallet and now on 694
i'm testing the node_v_0.5_beta version and at first everything is looking good
but it's stuck at block 689 for a while.
Does anyone have the same problem?
but it's stuck at block 689 for a while.
Does anyone have the same problem?
No transaction and will not be created blocks
read back already discussed the work Node
check now 690 block
my apologies, I didn't read
i'm testing the node_v_0.5_beta version and at first everything is looking good
but it's stuck at block 689 for a while.
Does anyone have the same problem?
but it's stuck at block 689 for a while.
Does anyone have the same problem?
No transaction and will not be created blocks
read back already discussed the work Node
check now 690 block
thx, i just wanted to ask the same. seems the client is working fine. gonna send some random transactions for testing
i'm testing the node_v_0.5_beta version and at first everything is looking good
but it's stuck at block 689 for a while.
Does anyone have the same problem?
but it's stuck at block 689 for a while.
Does anyone have the same problem?
No transaction and will not be created blocks
read back already discussed the work Node
check now 690 block
i'm testing the node_v_0.5_beta version and at first everything is looking good
but it's stuck at block 689 for a while.
Does anyone have the same problem?
but it's stuck at block 689 for a while.
Does anyone have the same problem?
Development looks like it is coming along well!
Reading the past couple of pages of this thread has been a breath of fresh air in this FUD-SEWER of a forum... thnx!
I think part of the reason for that is because no one really knows about the coin. Hell, I've been following the thread for awhile and I have no freakin idea of the true status of the coin in terms of development. It could really use a vocal project/product manager.
But don't worry. I'm sure at some point the trolls and fudders will start to show up once they start to think this coin could threaten whatever coin they're holding. lol
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
How to get this coin?
NODE : BUY / SELL THREAD
https://bitcointalksearch.org/topic/node-buy-sell-thread-727745
@SillkRoad
Thank you for the answers but I take it English isn't your first language
Where does the database and wallet files get written to on my computer?
Thank you for the answers but I take it English isn't your first language
Where does the database and wallet files get written to on my computer?
Yeah, it's not my native language
c:\nxtl (when increase download speeds several times, will be the new name of the folder "Node")
@SillkRoad
Thank you for the answers but I take it English isn't your first language
Where does the database and wallet files get written to on my computer?
Thank you for the answers but I take it English isn't your first language
Where does the database and wallet files get written to on my computer?
Jump to: