Topic: deleted - page 21. (Read 68076 times)

Team is working on another technology for faster syncs and more efficient bandwidth usage.

But can't comment without a final working wallet.

Yes of course, bounty is still there.

Hardforkcoin, old name cause ABF was the primary feature of this.

See original ann.

https://bitcointalksearch.org/topic/annhardforkcoin-720181

Is there still a bounty?

 

HFC really stands for huge fast Coin.  Doesn' t it.  Tell us the truth.

Proxy support for the alpha client coming up...

Ok.

A comparatively cleaned ann.

Details moved to website.

Tell me if it has to be shortened more.

Yeah, I'll move the research work to the website.

Thanks for the advice.

be careful doing a giveaway here. you might get locked from the thread.

Could you put a section in OP with coins specs. like all the coins have.

block rewards break down.
time per block
how many pow coin.
is this pos? if so how many pos %

etc


please also try to clean up the OP and formulate your message and the coins purpose a bit better so it will be easy to follow. this looks interesting but its so hard to follow throw that wall of text.


Thanks!

7dcaee4cb51f3a40154380cbfc5b5d87e3340c638c108d89f74773ce22e52e6d

2000 HUGE paid for downloading wallet.

9.3.0.0 (beta) with TLS server support; or in simple terms, this wallet is completely backwards compatible with the old protocol. It can take incoming connections from both the old protocol and the new one (compressed, encrypted), but it only makes outgoing connections using the old protocol.
http://www.hardforkcoin.org/BIGcoin-9.3.0.0.zip
https://github.com/hardforkcoin/bIGcoin-9.3.0.0-beta

Alpha (with TLS client support). This is just like the above (9.3) but when making outgoing connections, it's going to use the new protocol (TLS 1.2 encryption + compression).
https://github.com/hardforkcoin/BIGcoin-alpha
http://www.hardforkcoin.org/BIGcoin-alpha.zip

With the alpha version, you'll see the cipher and keybits in getpeerinfo.

-minkeysize switch also exists.

Coming soon; 'dumpcert' command.

It depends on how many votes have been casted for the winning category.

Suppose, girl 1 wins with 4 votes. So each voter gets 10000/4.

You have to PM the OP with your BIGcoin address and your choice.

How do you get paid and how much.


and why?

Didnt mention about the new switches

-certkeysize: Specify key size of the generated private/public keypair for TLS connections. Defaults to 2048.
-minkeysize: Minimum keysize which is required to connect to an outbound connection. Defaults to 2048.

TLS (SSL) v1.2 secured connections (better than tor)


{
        "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 port
Current 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 compression

BIGcoin 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.

How protocol migration is done
Suppose BIGcoin team wants to implement protocol changes; using ABF this can be consistently done without a single fork or refused connection.
Assuming wallet C as the current wallet version running the old protocol. Wallet Z is the version fully implementing the protocol and completely incompatible with C; i.e. it neither of C or Z accepts each other's connections. X and Y are intermediate versions of the wallet released between versions C and Z. X accept connection from both the new and old protocols (it's compatible), but does not connect using the new protocol. Y is just like X but connects using the new protocol.

Sorry for the delays.

Writing content for the new features. Will update top post as soon as it's made.

This is the 9.3 wallet.

http://www.hardforkcoin.org/BIGcoin-9.3.0.0.zip
https://github.com/hardforkcoin/bIGcoin-9.3.0.0-beta

This also listens as a TLS v1.2 server. Try connecting to the wallet running on your local system with --

$ openssl s_client -tls1_2 -connect 127.0.0.1:14351

Certificates are generated dynamically on startup.

This wallet works in 'dual mode', it detects if the incoming connection is TLS or unencrypted BIGcoin protocol and acts accordingly.

Ok, the GIT repository is 9.2 again.

9.3 has been fixed. To be released soon.

9.4 will be released only as source.