[UNOFFICIAL] [VNL] Vanillacoin 0.4.1 | Instant ▱ Incentivized ▱ Innovative

[monsterer]

Transactions can stay in the global transaction pool for up to 72 hours before being completely removed. Even if it were to be removed both the sender and recipient rebroadcast it every 120 seconds until it is satisfied. Obviously since the subject block is conflicting with the global transaction pool it is rejected by all recipients. No amount of hash-power can obtain more than 1/3 of the consensus by design so the hash argument is moot here. The source code is freely available for inspection. Bitcoin doesn't to my knowledge do any of this extra protection.

Thank you for your support.

edit: what is the point of having transactions remain in the mempool after they've been written to blocks? You cannot have two different, conflicting consensus mechanisms.

[1714786368]

1714786368

[1714786368]

1714786368

[1714786368]

1714786368

[YarkoL]

edit: what is the point of having transactions remain in the mempool after they've been written to blocks? You cannot have two different, conflicting consensus mechanisms.

Apparently mempool takes precedence, so conflicting transactions
whether in block or not are rejected. So no conflict remains.

[TheProf]

Nice move on price...

[etoque]

Good uptrend... with not so much volume... Could see new ATH soon 

[najzenmajsen]

Nice move on price...

Indeed, and best of all it seems to be a natural uptrend and not a pump.

[monsterer]

Apparently mempool takes precedence, so conflicting transactions
whether in block or not are rejected. So no conflict remains.

The only way that would work is for every single transaction that was ever made to remain in the mempool. Now, what kind of collection of objects do you know of that behave that way? (hint, it has 'chain' in the name)

[YarkoL]

Apparently mempool takes precedence, so conflicting transactions
whether in block or not are rejected. So no conflict remains.

The only way that would work is for every single transaction that was ever made to remain in the mempool. Now, what kind of collection of objects do you know of that behave that way? (hint, it has 'chain' in the name)

That's right   New transactions are checked against block database
first as usual. But block is only accepted if  the transactions that it contains  
(apart from coinbase) did not conflict with the ones
in mempool.

It's different in Bitcoin, where the block contents override the mempool.

[monsterer]

That's right   New transactions are checked against block database
first as usual. But block is only accepted if  the transactions that it contains  
(apart from coinbase) did not conflict with the ones
in mempool.

It's different in Bitcoin, where the block contents override the mempool.

So that means that any new transaction which is accepted in the mempool can cause the entire blockchain to reorg, all the way back to the genesis block?

[YarkoL]

So that means that any new transaction which is accepted in the mempool can cause the entire blockchain to reorg, all the way back to the genesis block?

AFAICS it will not be accepted if it conflicts with the ones
already in the chain.

[monsterer]

So that means that any new transaction which is accepted in the mempool can cause the entire blockchain to reorg, all the way back to the genesis block?

AFAICS it will not be accepted if it conflicts with the ones
already in the chain.

That's the opposite of what you said in your last reply.

[SquidsIn]

i have some ZTEX FPGA with Spartan 6. Can i mine with this board: http://www.ztex.de/usb-fpga-1/usb-fpga-1.15y.e.html

I would be very interested in this too, I also have some Quad Spartan 6 Cairnsmore CM1's.

For now I shall just buy VNL at these low prices but it would be nice to mine some for posterity, this ones a keeper.

[YarkoL]

That's the opposite of what you said in your last reply.

How so?
New transaction comes in.

Does transaction conflict with one in the database (in blockchain)?
Yes. Reject it.
No. Does it conflict with one already in the mempool?
Yes. Reject it. No. Accept it.

Eventually it shows up
in a block and is removed from the mempool.

New block comes in. For every transaction in the block:
Does the transaction conflict with one in the database?
Yes. Reject it.
No. Does it conflict with one in the mempool?
Yes. Reject it (here's the difference with btc).
No. Check next transaction if this is not the last one.

[pallas]

PSA

Since BCT passwords and usernames were compromised please don't forget to change your passwords here and on the other services reused them.

also remove the security question.

BTW: http://www.engadget.com/2015/05/25/google-security-question-study/

This is the second time someone posts exactly the same thing I did some days before.
Clearly they are new users trying to get some trust by posting. Makes me think they are scammers or trolls so beware.

[monsterer]

New block comes in. For every transaction in the block:
Does the transaction conflict with one in the database?
Yes. Reject it.
No. Does it conflict with one in the mempool?
Yes. Reject it (here's the difference with btc).
No. Check next transaction if this is not the last one.

It bitcoin, when a new block 'comes in' all the transactions have already been mined from the mempool and committed to the blockchain. What you are suggesting is that the miner of block B also revalidates all transactions from block A against the mempool - this leads to a situation where miner B will generate a fork of N blocks if a disagreement occurs (N = 2 in this example).

[traumschiff]

New block comes in. For every transaction in the block:
Does the transaction conflict with one in the database?
Yes. Reject it.
No. Does it conflict with one in the mempool?
Yes. Reject it (here's the difference with btc).
No. Check next transaction if this is not the last one.

It bitcoin, when a new block 'comes in' all the transactions have already been mined from the mempool and committed to the blockchain. What you are suggesting is that the miner of block B also revalidates all transactions from block A against the mempool - this leads to a situation where miner B will generate a fork of N blocks if a disagreement occurs (N = 2 in this example).

Jump on IRC, John is here if you would like to have a discussion with him.

https://kiwiirc.com/client/irc.kiwiirc.com/vanillacoin

[hokus_pokus]

ill just leave this here  

"if you follow the design i have put in front you'll see i created an encrypted dark net"

 "vanilla with UDP will be 100% a dark network"

Wow...I knew about this from the beginning but with UDP implementation that takes this to another level. Darker than dark baby! And phone application lite...excellent work

[monsterer]

Jump on IRC, John is here if you would like to have a discussion with him.

https://kiwiirc.com/client/irc.kiwiirc.com/vanillacoin

I just find it rather odd that the whitepaper doesn't describe the consensus process at all - for something claiming to be so revolutionary, it really should be described in full in the whitepaper.

[Jookly]

Jump on IRC, John is here if you would like to have a discussion with him.

https://kiwiirc.com/client/irc.kiwiirc.com/vanillacoin

I just find it rather odd that the whitepaper doesn't describe the consensus process at all - for something claiming to be so revolutionary, it really should be described in full in the whitepaper.

It is the code that describes it in full.  Not saying I understand it.  But the proof is in the code not in the description of the technology.

[traumschiff]

Jump on IRC, John is here if you would like to have a discussion with him.

https://kiwiirc.com/client/irc.kiwiirc.com/vanillacoin

I just find it rather odd that the whitepaper doesn't describe the consensus process at all - for something claiming to be so revolutionary, it really should be described in full in the whitepaper.

As Jookly mentioned above, you can freely review all the code on github, trying to force a discussion on BCT without John being here is kind of pointless. It was mentioned several times here that John spends most of his time on IRC when he is online and working (almost everyday). Feel free to jump on IRC and ask away about anything that you doubt.

Else I'm happy about the technical discussions that take place here, but I would really encourage you to ask them directly to John since you seem to be really curious.

[traumschiff]

PSA: UPDATE SOON & POW resumes at block #136000

Current block: #132967

An update will roll out before this happens. Jump on IRC for more information.

Thread regarding the update: https://talk.vanillacoin.net/topic/143/temporary-proof-of-work-pause-at-block-117833/11

Update in the thread:

There will a mandatory network-wide upgrade tonight 8PM EST to 10PM EST. Proof-of-Work mining will resume at block 136000 after the upgrade. You will receive an upgrade alert as a reminder in about 1.5 hours.

Thank you for your support.