![](http://web.archive.org./web/20230626042204im_/https://styles.redditmedia.com/t5_2zhk3/styles/communityIcon_e2ah1kvwcjy61.png?width=256&v=enabled&s=dae2c517951cacb25edd281e377bec9ac659af5d)
Dogecoin Development
r/dogecoindev
Hello Shibes,
I did so much more things in the last months but because Im mostly on twitter I fogot to also update here :)
The most recent is ShibeShip.com MarketPlace that enables any one to Buy/Sell things only in Doge, worldwide with automatic verification of payments and with a new type of security for the buyer and seller using a 6 PIN phrases to encrypt the LibDogecoin Adddress Generator that I use, soon will also finish the implementations of GigaWallet on it.
I ask everyone in the community to test it and because is in Beta to be carful because it uses real money. If you find any bug or anything I can improve please tell me. My code is OpenSource on my Git https://github.com/qlpqlp and will update also later with this new improvements that I'm doing on my local computer
Found a bug thanks to https://twitter.com/UsaRandom on https://ShibeShip.com that didn't allowed to register.
If you tried to register in the last 2 hours, please register again and you should receive an verification email to activate your account 🌝
Not sure if https://blockshibe.net is up right now but looking at the mempool from https://chain.so/DOGE and https://nformant1.github.io/mempool.html we are seeing an unprecedented surge in transactions. Our blocks are basically full.
First order on the agenda should be to revert the blocksize restriction of 750 kb to default to 1 mb which we have talked about several times previously.
It is important for us to understand what is happening right now. There has been doginals for months now and we saw doubling of blockspace usage from about 1.5% to 3% and then back to 1.5%. But now we are likely above 50%. They timed this attack with the launch of basically useless 'DRC-20' tokens. The only way I could see this organically creating this surge would be if each token created takes a transaction. If someone is creating 50,000 'dogeclub' tokens or whatever they are doing, if that took 50,000 transactions then I could see where this is coming from. Is that the case?
Bitcoin has been under attack for months now. Litecoin is not so much. It is strange when I look at recent doge transactions there are groups of a half dozen transactions of all the same value. A group around $10 each, then a group around $31 each, a group around $62 each etc. It is also strange to me that this comes right after someone asks when we are going to come out with 1.21, which to me means they were fishing to see if we were about to activate segwit. If we were then they would probably have waited to launch the attack after we had segwit and they could make even bigger ordinals to clog up our blockchain even more. Good thing we aren't. Since we don't have segwit, inscriptions can only be 256 characters and 1.5kb per transaction https://captainaltcoin.com/mint-drc-20-tokens/ . Pay to script hash is bieng used to pull this off https://github.com/apezord/doginals which we regretably pulled from bitcoin bip16 https://github.com/bitcoin/bips/blob/master/bip-0016.mediawiki . Is there a way we can revert the ability to have arbitrary data OP codes in P2SH? In my opinion we should never added a basically unremovable attack vector like a new address format (P2SH) at all. One signature per transaction is what blockchain was created to do.
I think we also should be exploring what optimizations ethereum used while they were PoW to get orphans minimized with a 12 second blocktime, and we should be running testnet to try out faster blocktimes. By the looks of it, if this is an orchestrated attack with a facade of bieng organic demand, it probably won't stop. And if it does relent, there will just be another new attack in the future, like from nft's originally to now tokens, and who knows what the next attack will be and what excuse they will use to cover their motives. We can see the relentless attack on bitcoin and they are coming after us too.