Please advise what are the further steps to take from here.
Release your whitepaper and make sure someone do peer review on your paper. Release it on it's own testnet or release the source code also helps.
There was never an issue with figuring out the way to scale a blockchain, there was just a debate on which solution we will implement.
That debate resulted in a fork as people couldn't agree.
I disagree since there's few lazy scaling solution such as only increase maximum block size limit while others try to decrease TX size, move it to off-chain/2nd layer or make nodes not verify all transaction.
The lightning network works only in theory because it still needs everyone to be in a payment channel with someone. Just writing those "LOCKED" payment channels requires a lot of on-chain space.
You mention LN's disadvantage, not why it only works on theory since LN already used on both testnet and mainnet.
I am glad that you have another solution, but this is a 'problem' that even Satoshi gave a simple solution for.
It is a kinda of a virtual problem, not a natural one. The block limit was purposely implemented for spam protection.
So it is very simple if you just want to solve it simplest and quickest way possible, but off-chain solution ended up being followed by most.
Here's my view for your statement. If 10 billion people in the world used blockchain for payments. That's at least a million transactions a second. Currently, the Blocksize is 1 MB. If the minimum BTC transaction size is 250 bytes. ~4,000 transactions per block. That's 6.66 Transactions per second.
I have a solution (proof of concept in GoLang) which scales up to 1M transactions per second with a smaller block size without compromising on decentralization / security / future scalability.
Assuming current block size is 1MB (which isn't because we use block weight limit with 4 kWu limit) or AFAIK 1.000.000 bytes in reality, then that means 1 transaction only have size about 1 byte and i can't see how would you fit transaction (input, output and signature). But i've no idea about GoLang.