segwit2x does have a codebase
https://github.com/btc1/bitcoin/

https://github.com/btc1/bitcoin/blob/segwit2x/src/consensus/consensus.h
segwit2x now has code for a 2mb base block
33    if (!BIP102active(nHeight, fSegwitSeasoned))
34        return MAX_LEGACY_BLOCK_SIZE;
35
36    return (2 * 1000 * 1000);
37    }
...

which activates 3 months for th 2x after segwit
13    static const unsigned int BIP102_FORK_BUFFER = (144 * 90);

..

but not really a Release Candidate so its highly possible the pools flagging for segwit2x are not running the codebase
so all the flag waving of blocks is still kind of 'sybil' (empty/fake gesturing). so things are still up in the air.


the hong kong/ late 2015 consensus round table meetings  funded and sponsored by barry silbert.. is the same 'agreement' as segwit2x
but atleast there is some code available.

now we just have to see if we can get nodes to download it (once its finalised and reviewed for RC) to then get a NODE consensus... for pools to have confidence that if they made such blocks.. the nodes wont still be running old code to reject blocks bigger than (1*1000*1000).

what people seem to forget is its not simply about waving a flag in a block.. its about consensus of nodes actually running code rules that allow bigger base blocks and consensus of pools creating bigger base blocks.

at this moment the empty sybil flag waving will just cause segwit to activate, but no guarantee of base blocks over (1*1000*1000) being accepted because from bitnodes stats, it shows no one is actually running the segwit2x (btc1) codebase to enforce it

p.s only reason i rant/repeat myself. is due to the biased censorship deleting my posts to hide the facts, so i end up having to repeat things just for the hope that some posts get missed out in the deletions so that they actually get read.. because alot of the facts just get deleted. i would repeat myself alot less in topics if it wasnt for moderation deletions