I guess that Joe Six Pack learned that transactions fees per transaction could reach $55 each and ran away from the
doors of the casino instead of coming inside.

Blame China, Korea, India or even Putin but since fees peeked you can clearly see that Bitcoin has been going down
but the development team and miners want you to blame everyone else but them.

 

"What Caused the Boom in Bitcoin"

Well Bitcoin was doing sort of OK using Tor to sell weed and a flash of tit's but about 14 months ago
it took off after WannaCry type viruses popped up all over the place forcing people to pay a ransom
payment using Bitcoin.

These payments were used as seed money for the boom I thinks and Tor does not get a clean bill of
health from me by any means so read in to that what you like.

Not only should you sell your house but get your mother to sell her's too.

I know someone that knew someone who lived next door to the sister of a man who
won $3m on Lotto Football and if you don't play Lotto then you cannot win 

Yes if i keep feeding the fruit machine with more coins, it got to pay out sooner or later and i love listening to
"Clunk, Clunk, Clunk" when it pays out and everyone looks towards me but funny thing is that it's makes no noise
when your feeding the machine with all your hard earned money.

Nope and as a beginner you need to jump in now to bale the other gamblers out who want to take their winning
home with them.

Just think you can play with the Lightning network and learn how high fees and interest rates can go
using the banking hubs as part of your education but do be warned fees can reach $55 per transaction
the next time you come across the term "Virtual free transaction charges" because that was the manter
they used with Bitcoin in the past and it's not worth the paper it was not even printed on.

  

Was you the guy who told me to "Buy on the dip-stick" the last time BTC was at $18k because it sure sounds like you.

it would had gone to $50k i think but the miners got too greedy to early and didn't reel in the new meat but instead
put transaction fees up to $55 so yes the public all now know about Bitcoin and won't be coming to play for this reason.

Noticethe old lags pumping outdated posts back to the top of the forum ? They are getting desperate to hide
real facts and news here.

Well all the ones with more than 20 channels open, you know ran by the miners because only they have the hardware, skills and BTC to run
these banker hubs and past history shows just how much we can trust these miners.

if it charges transactions fees and interest on the BTC to keep the ledger open, it's a bank

$55 just to process 250 bytes of data is what has killed bitcoin and no one will trust the development team or the miners
ever again for this reason.

ETH didn't go down this route when they had a mad rush due to crypto-kitties and a lot of people who have educated themselves
about Bitcoin can see that the lightning network is both off-block and consists of banking hubs so I think it's game over myself and
the charts appear to agree with me but we will see.

I jumped out mostly at $18k due to fees being so high and warned people to put a stop-loss on at $10k so my track record is quite in-tacked
when it comes to looking in a crystal ball.

The block-chain is missing the block-ledger and it is this that will allow it too scale because the data becomes 3 dimensional instead of two
and lets forget trying to make out that it's anything more than it is because it's a linked list with hashcodes pinched from Bit-torrent and it's not
like someone found a replacement for OO or anything to write home about, it's nine years old and just won't scale as implemented by Bitcoin and ETH

I don't think people are quite picking up the point here or maybe I didn't put it across correctly but we are not talking about
encrypting small amounts of data like a 2k whats-app message but something more like 100k needed for the HTML on a web-page
and then six javascript files within the page followed up by say ten 2mb .PNG/Gif images files and a CSS file

Performance is critical here because if these requests are not serviced within 2-5 seconds then the browser will try sending the request again
using multi threaded requests so both the client and server nodes need to also be multithreaded also and the exit nodes need to start pumping the data
back across the network even before they have the whole reply from the web-site.

Things are made worse because often data is chunked which more or less means streamed and you have relay nodes possibly in the middle
plus having to service 100 requests all at the same time so buffering up the data to be encrypted in memory and keeping much state information
simply is not an option.

Data can be sent over TCP/IP as a 30K message but can be received as three 10k sections with a second delay between them all
but you still have to start feeding the web-browser as soon as you receive the first 10k or else it might timeout so I have no option
but to use on-the-fly stream encryption and it must perform like Greece lightning.

What i do know is that Microsoft AES encryption works nearly as fast as I can iterate over a byte array
using un-safe code from C# with C++ style pointers so I don't know if specialist hardware is being used to
get the performance for AES encryption but that's the type of speed that I need and using Maths.Mod or BigINT's just won't
give it to me

Microsoft's AES encryption memory leaks and I am not trusting back-door bill gates with any keys or data given that
I don't know whats being copied and uploaded back to the NSA/CIA servers all night long.





Yes got safe key exchange using Bitcoins Secp256k1 on a control channel and the data-streams have good encryption
on the HTTP Requests send to the server nodes but these requests are only between 400-2000 bytes in size so no trouble to encrypt.


8K chunks are no use when
sending 2mb images over the internet and often using relays, not going to work that's not.


Google is trying to use UDP instead of TCP/IP for web-pages with the Chrome browser but I am not doing anything apart from
DNS using UDP:53

I keep the control channel and a number (Six just now) of these bi-directional streams open per client so that a node sitting behind a firewall
can still act as a server but in general the number of streams needed to service a web-browser can reach as high as 30 steams at a time

in my quest to find what i was looking for I took the code here, nice sweet and simple it is and it used maths.mod to encrypt data
and I got it up and running in seconds ready for a bit of benchmark testing on 1GB of data (1mb blocks).

https://www.codeproject.com/Articles/17703/Stream-Based-Encryption-for-NET

I stopped the program after about sixty seconds and it had only managed to encrypt/decrypt
500mb of data so i think you can have good encryption or fast performance but you cannot have both.

BigINT are useful for encryption but again I just cannot get the performance I want using this method.

My current plan is to semi encrypt the data, tweak the key and pass it over to Microsofts black box
encryption but I won't be using AES encryption because the .NET version leaks memory which you only get
to see if you call it half a million times or so which might sound a lot but a proxy server can reach these
type of number in little over an hour.

 

That sounds like how many machine code instruction cycles does it take to encode each bit which is
related to the speed of the CPU so you want a low number of cycles and a high clock rate to get any speed

https://github.com/TangibleCryptography/Secp256k1/blob/master/Secp256k1.Core/ECEncryption.cs

The ECPoint gets encoded with with a AES key and IV



Later these are used for the signature signing


So the hard coded value seem to be correct and I think I had looked in to this before so I just took it that the rest of the
code would work with bit-coin since it contained the Base58 and Hash160 code but somewhere along the way it seems
like it come off the rails

Thanks for the link and you gave me the right answer in the end after looking around and finding very little code that would run in windows let alone
in C# that would stream or was open source and would give me any performance let alone not being bloatware that falls back on BouncyCastle or being open source.

you see I can encrypt something in Dot-spyware-net in about five lines of code but i don't trust them so what i think I might do is to semi encrypt
the stream, chuck it to Microsoft's black box code after reversing the key or something and then reverse the process during decryption.

I need to do some banchmark testing but why re-invent the wheel when only a spoke is broken and I might even throw in some compression
whilst I am about it.

what does concern me is the open source Secp256k1 code that I picked up and was planing on using for key exchange because it's starting
to look tainted now and I do confess that I don't really understand the maths behind points on a wave and this bit of code is starting to look
suspect to me.


Does anyone recognize these hard coded strings ?

Yes i am starting (I think) to get the picture and the code I got this impression from was from here
https://github.com/TangibleCryptography/Secp256k1

Seems to tick all the boxes if you care to look

See second post here https://bitcointalk.org/index.php?topic=2826752.msg%msg_id%

I think this code was hanging around in the forum from about 2014
https://bitcointalk.org/index.php?topic=574882.0;prev_next=prev

The ECPOINT in his code uses key exchange from Secp256k1 for AES key/iv as you can see so
I am not sure whats going on here so maybe you can cast some light on this and excuse me for
saying that Bitcoin used AES

I started to suspect something might be wrong (late in the day) when I noticed the name "Brainwallets"
and I would give you a merit for correcting me but I don't seem to get many to give away around here so
it will just have to be a kiss 

I am not anyone and ho fucking dear, I have seen that name which i will come too.



I don't think I have many other options, encryption is ten a penny but unfortunately not just anyone will do.


I pulled the bitcoin Secp256k1 from a windows library and I use that for key exchange because it is second to none
but after that the code in Bitcoin uses AES for the signature from what I had seen. Here is the code that's in the project I pinched the Secp256k1 from.

I could dig deeper into this but here is another bit of code from the same project !


The header for encryption reads


This is why I stated that Bitcon uses AES after key exchange but now I have to question this myself
but this project I pulled this code from is quite a common one so I am not sure what to make of this.

Encryption is no use if it's too slow and in my case cannot be streamed and unfortunately for the PTB
I tend to trust my own judgment.


Yes Linux is better but I am too much of an expert with windows and the bloated .NET framework to just jump ship, too old too.


My code would be open source and must stand up to peer review and I am sure no one would say a world if i just pasted the AES keys over to
microsoft to process the encryption because that's just whats happen already with windows based wallet on Bitcoin so please don't knock me for
at least trying something new.

here is what I am trying to deal with

Browser --------Entry-Node------Relay-Node--------Exit-Node-------Web-site

The trouble is some web-sites use chucked data and pages are not simply send as <HTML>........</HTML>
but are sent as 'Chunks' for the browser to process and waiting for the exit-node to collect and then encrypt the
whole page is not an option and you have to bear in mind that the entry node might no receive the data as one
big long packet.

Throw in that nodes are stateless apart from knowing the key and you start to see what I am up against and i just tried
putting in a few flag switches on the encryption but that didn't work because packets might be sent out as
[------100k-----------][------20k-----][--------50k--------]
but could be received as
[--1k---][---2k---][----something k-----------------------]

lucky I already have good encryption working on the HTTP request headers used to set up the circuit
but i don't think much more can be done on the payload of the page without breaking some pages so it's
a toss up between good encryption and broken pages as I see it.

1GB encryption/decrytion in under ten seconds is not something that I can just pick up off the shelf or I would believe me.

it says

performance wise it's going to be too slow compared with


I could do something using BigInts with a bit of maths on 64 bits of data but it needs to stream
and the CPU would be running at a high rate and inserting markers into a byte array means copying the
array to make the space needed so again that's not an option.

Will keep banging away and let you know if I find a solution 

This is not so easy as you think on windows and I want the code in C# and not as a Dll since I want my program
to work as a single stand alone .exe

I am not after bloatware where you need 5,000 lines of code, it must be fast and work on the fly so it can be
used with a socket stream so that movies and big files can be streamed across an unreliable network.

Just buffering up the data before sending it back in a fixed sized blocks on the server nodes is not really an option
and even then the client might not receive the block on the network as a full block so this is why I am after on-the-fly
encryption.