TLS (SSL) v1.2 secured connections (better than tor)$ openssl s_client -tls1_2 -connect seed.hardforkcoin.org:14351
CONNECTED(00000003)
depth=0 C = GB, O = BIGcoin, CN = My IP
verify error:num=18:self signed certificate
verify return:1
depth=0 C = GB, O = BIGcoin, CN = My IP
verify return:1
---
Certificate chain
0 s:/C=GB/O=BIGcoin/CN=My IP
i:/C=GB/O=BIGcoin/CN=My IP
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIC1zCCAb+gAwIBAwIBATANBgkqhkiG9w0BAQ0FADAvMQswCQYDVQQGEwJHQjEQ
MA4GA1UECgwHQklHY29pbjEOMAwGA1UEAwwFTXkgSVAwHhcNMTUwMzE2MDMyNjE4
WhcNMTYwMzE3MDMyNjE4WjAvMQswCQYDVQQGEwJHQjEQMA4GA1UECgwHQklHY29p
bjEOMAwGA1UEAwwFTXkgSVAwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQD0M5CcFgsUqK8kgfsQYS8gbpz6pu2v9CbfOCLuKH2K9niQKqU8nZuXGwhUTOO2
OLQhH5xypIrw271d+exTR/15P8tMCjGDnRKIIDNuc9JjBBjMdfjHMXzrCK++o1ij
wFgkMItTvmpImHgU7EYh0zsK/PSZRhXSbu6ejiCo1NP9BWWADxMECHHJd/1OQxsi
SYsQ8z5UaY/vpW7m5be7u1SDUdJ5kEykj+UqGJ+847y3ZxmlWVAnedcWq3VNj/UD
bnvg07ffAlN69psmgEdPfe3jrF4WsehQ2JXuBj7mUjzYAGZXNNOCAz6fAiCG6ksh
lgHby4UImzy0adJrjM924H61AgMBAAEwDQYJKoZIhvcNAQENBQADggEBAFxx5fRh
Zgr7opWLMe/LqHvQXfC3Bk9a6fJ468TlHTQZK27iXBQTh46l7mkcAZZVIo9m9tJM
9kK/XwUnIacOwyNDqgylkCWqbUPTgob5pALi6uPTSSnh1Jquw1gPsSNJkEnBzBQX
p4G8YlQ3rWMZ1VACK669ipJLUQq51e5aRMxPqxt9BI1ZeZqvyUjmdixnGNgrmoML
PQvuRS6cU8Oh9Kz+MTOG5sIkHwUXt2Uq/2jrCyi2EFyja5TudoF2R/g/N3TL1Krq
Yn3hvMb8vSQLvIQwh0D58Ri7A3sqEt+WaW9kmR/Zw5D2kQcqLIUZlKsawyYWQRRq
kRm+OIW3TqvqcOE=
-----END CERTIFICATE-----
subject=/C=GB/O=BIGcoin/CN=My IP
issuer=/C=GB/O=BIGcoin/CN=My IP
---
No client certificate CA names sent
---
SSL handshake has read 1053 bytes and written 635 bytes
---
New, TLSv1/SSLv3, Cipher is AES256-GCM-SHA384
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: zlib compression
Expansion: zlib compression
SSL-Session:
Protocol : TLSv1.2
Cipher : AES256-GCM-SHA384
Session-ID: 672E3DCA1E9E6A762A50C0580C9D7D7F27BAD635918EB33F00330FD0AC21A946
Session-ID-ctx:
Master-Key: EDA8C354209510C53F3D0DE7E3B350ABE5626977A25BBE8AA93829F84D37CB6798D528BEC6D2A3D97A5E2FE2BB251E7C
Key-Arg : None
PSK identity: None
PSK identity hint: None
SRP username: None
TLS session ticket lifetime hint: 7200 (seconds)
TLS session ticket:
0000 - 96 16 d0 71 8b a6 24 bf-21 f3 d1 06 ad dd 07 39 ...q..$.!......9
0010 - d5 7b 04 96 7a 8d 99 1a-3c 57 e0 3a bc 5f ca e9 .{..z...<W.:._..
0020 - 59 62 3d 55 90 af 2d 6d-a3 02 4e 7d 6f 0d ee 55 Yb=U..-m..N}o..U
0030 - 49 1e 1e 1f 04 14 dc cb-12 74 6b 9b bb 9a e5 5e I........tk....^
0040 - 13 24 f3 7f 9b 02 5b 0b-b9 84 c8 87 83 7f 42 46 .$....[.......BF
0050 - 81 28 f2 ed 79 fa d2 44-f3 c7 b6 b5 f1 04 0c 36 .(..y..D.......6
0060 - eb 88 e8 d5 10 6a 79 28-aa 66 a8 a8 0a 5a e0 a1 .....jy(.f...Z..
0070 - 76 9f 37 2f 49 dc 26 27-60 41 3d 6e 83 85 f0 62 v.7/I.&'`A=n...b
0080 - b6 f8 84 a3 16 73 e1 42-8c bd cc 43 1d 48 01 2b .....s.B...C.H.+
0090 - 23 43 c4 95 1e 67 0a a0-0c 58 bc b2 4f 6f a5 39 #C...g...X..Oo.9
Compression: 1 (zlib compression)
Start Time: 1426698460
Timeout : 7200 (sec)
Verify return code: 18 (self signed certificate)
---
{
"addr" : "103.242.119.194:14351",
"services" : "00000001",
"lastsend" : 1426698809,
"lastrecv" : 1426698808,
"bytessent" : 1223,
"bytesrecv" : 146,
"conntime" : 1426698808,
"version" : 70001,
"subver" : "/Blake:9.3.0/",
"inbound" : 0,
"startingheight" : 565221,
"banscore" : 0,
"cipher" : "AES256-GCM-SHA384", "CertificateKeySize" : 2048, "syncnode" : 1
}
Connections made by the BIGcoin wallet is encrypted using TLS v1.2; thus your IPS or network administrator or the government has no idea what you're doing making the BIGcoin protocol completely anonymous.
Without this feature blockchain obfuscation (DarkSend, Ringsignature) is completely transparent if the ISP or network administrator or the government is spying on your activity; actually it's worst, they all know all the addresses you own and what you're doing with your money regardless of the blockchain obfuscation you're using, since this is done at a protocol level.
Tor can be almost completely be
blocked using the list of known exit nodes, but doing the same for BIGcoin is not possible (see Randomized listen port) since there is no such list of exit nodes.
Tor is a
high latency network. That's the reason why using video/audio conferencing is not popular when using tor. Blockchain technology relies on low latency network for proper operation, otherwise the miners are at a loss following increase in number of orphans, specially when block times are low to support faster transactions and higher network scalability.
Besides it's questionable if Tor's 7000 relays can support Bitcoin's 1 million transactions per day and 6200 full nodes with it's downloading of 23 GB blockchain. It's not know how the Bitcoin network will function with the high latency tor network.
BIGcoin's TLS implementation gives tor-like anonymity with an efficiency more than the native Bitcoin protocol.
See "Network synchronized updates" for migration plans to full TLS 1.2 secured networks.
Randomized listen portCurrent status: pending
BIGcoin's default port has been changed to 443, the default SSL port for HTTP traffic; in case it's not able to bind to this port, it's going to choose a random port.
This along with protocol encryption makes blocking or detecting BIGcoin protocol next to impossible.
Transaction broadcast uncertainty.BIGcoin protocol is undergoing heavy development and this TLS feature is not complete. This technology is currently pending.
Protocol compressionBIGcoin uses Zlib compression to improve on latency and reduce data usage, making the networks much more scalable and capable of handling more transactions per second. In our tests, our syncs were 22% faster. Expect more savings in a transaction heavy block chain with large blocks.
Because of lowered latency, expect less orphans especially when the block size grows to larger amounts.
