Closed Thread

[mrvegad]

A block is generated at a 60 s interval.

Is this different from the original code, or did I misunderstand BlockGenerator.prototype.handleVerifiedPeer?

Containing at least 1 transaction. The Empty transaction issue is ignored as the mining concept is removed.

So if I make a transaction and then no-one else does, what serves to secure my block?  How can we trust the ledger state without a continuous volume of transactions?

I'm thinking that since the txs is confirmed by many nodes then a block is made and since the txs in the block have already been confirmed then the block is secured and becomes part of the blockchain or whatever it is called.

[HunterMinerCrafter]

I'm thinking that since the txs is confirmed by many nodes then a block is made and since the txs in the block have already been confirmed then the block is secured and becomes part of the blockchain or whatever it is called.

The intent of a blockchain is to secure a time-stamped historical log by proving that time has passed since the history was logged, and that the network as a whole has agreed this time has passed.

What prevents someone from warping the clock consensus of the network with a classic Sybil attack?

[TaunSew]

If there is demand for CNY?

If you use coinmarketcap, most alternates have between 5% to 60% of their volume being CNY and another big percentage being BTC on Chinese exchanges.  I would say the demand looks sufficient for CNY.

[mrvegad]

What if each node has to go through a ntp check on startup to make sure they are within a certain time frame (can't more then 10 secs out)? When a node sends a txs it is checked against other nodes to see if it falls within that time frame, if not then that txs gets rejected and the node that sent it would get blacklisted. There would have to be checks in place to stop someone from adjusting the time once your node is running.

There is a crypto out there that does this, it is still in beta but it works. I don't want to give the name because for personal reasons I don't want to give support to the crypto.

[rabbiter]

When an exchange coming?

[mladen00]

When an exchange coming?

in aprox. 2 weeks

[hashpuppy]

How to get this coin?

[SillkRoad]

What if each node has to go through a ntp check on startup to make sure they are within a certain time frame (can't more then 10 secs out)? When a node sends a txs it is checked against other nodes to see if it falls within that time frame, if not then that txs gets rejected and the node that sent it would get blacklisted. There would have to be checks in place to stop someone from adjusting the time once your node is running.

There is a crypto out there that does this, it is still in beta but it works. I don't want to give the name because for personal reasons I don't want to give support to the crypto.

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

At Node double verification blocks
- When the blocks generates all of its peers are checked for validation
- At the start of the client

Node checks the transaction and blocks
- Not validate the transaction will not be added to the block,
- Not valid block will not be added to blockchain

Therefore, we take more time beta testing we want to debug the Node.

We are preparing a white paper, you will soon learn the full functionality of

[mrvegad]

@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?

[SillkRoad]

@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?

Yeah, it's not my native language 

c:\nxtl (when increase download speeds several times, will be the new name of the folder "Node")

[dodgecharger]

How to get this coin?

NODE : BUY / SELL THREAD
https://bitcointalk.org/index.php?topic=727745.0

 

[patmast3r]

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

[Viper1]

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

[dawj20]

Development looks like it is coming along well!

[luckygenough56]

 

[Arux]

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?

[SillkRoad]

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?

No transaction and will not be created blocks
read back already discussed the work Node

check now 690 block

[bitdraw]

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?

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

[Arux]

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?

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 

[mellorbo]

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