monsterer
Legendary
Offline
Activity: 1008
Merit: 1007
|
|
June 11, 2015, 01:15:42 PM Last edit: June 11, 2015, 01:39:33 PM by 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.
|
|
|
|
YarkoL
Legendary
Offline
Activity: 996
Merit: 1013
|
|
June 11, 2015, 02:07:59 PM |
|
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.
|
“God does not play dice"
|
|
|
TheProf
|
|
June 11, 2015, 02:28:12 PM |
|
Nice move on price...
|
|
|
|
etoque
Legendary
Offline
Activity: 1988
Merit: 1000
|
|
June 11, 2015, 04:42:44 PM |
|
Good uptrend... with not so much volume... Could see new ATH soon
|
|
|
|
najzenmajsen
|
|
June 11, 2015, 07:55:55 PM |
|
Nice move on price... Indeed, and best of all it seems to be a natural uptrend and not a pump.
|
|
|
|
monsterer
Legendary
Offline
Activity: 1008
Merit: 1007
|
|
June 12, 2015, 08:32:45 AM |
|
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
Legendary
Offline
Activity: 996
Merit: 1013
|
|
June 12, 2015, 09:57:52 AM |
|
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.
|
“God does not play dice"
|
|
|
monsterer
Legendary
Offline
Activity: 1008
Merit: 1007
|
|
June 12, 2015, 11:04:35 AM |
|
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
Legendary
Offline
Activity: 996
Merit: 1013
|
|
June 12, 2015, 11:10:29 AM |
|
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.
|
“God does not play dice"
|
|
|
monsterer
Legendary
Offline
Activity: 1008
Merit: 1007
|
|
June 12, 2015, 12:08:40 PM |
|
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
|
|
June 12, 2015, 01:55:00 PM |
|
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.
|
Since getting into Cryptocurrency I've had many bags, all but two have varied over time. Those are the two I see in the mirror where my eyes once shone.
|
|
|
YarkoL
Legendary
Offline
Activity: 996
Merit: 1013
|
|
June 12, 2015, 04:00:25 PM Last edit: June 12, 2015, 05:04:13 PM by 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.
|
“God does not play dice"
|
|
|
pallas
Legendary
Offline
Activity: 2716
Merit: 1094
Black Belt Developer
|
|
June 12, 2015, 04:28:42 PM |
|
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
Legendary
Offline
Activity: 1008
Merit: 1007
|
|
June 13, 2015, 11:06:01 AM |
|
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 (OP)
Legendary
Offline
Activity: 1498
Merit: 1001
180 BPM
|
|
June 13, 2015, 11:09:44 AM |
|
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
Member
Offline
Activity: 113
Merit: 10
|
|
June 14, 2015, 04:43:48 PM |
|
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
Legendary
Offline
Activity: 1008
Merit: 1007
|
|
June 14, 2015, 04:54:26 PM |
|
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
Legendary
Offline
Activity: 1131
Merit: 1007
|
|
June 14, 2015, 04:57:19 PM |
|
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 (OP)
Legendary
Offline
Activity: 1498
Merit: 1001
180 BPM
|
|
June 14, 2015, 04:59:22 PM |
|
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 (OP)
Legendary
Offline
Activity: 1498
Merit: 1001
180 BPM
|
|
June 14, 2015, 08:50:11 PM Last edit: June 15, 2015, 12:16:09 AM by 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/11Update 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.
|
|
|
|
|