Shiba Inu community divided over allegations of code, chain ID plagiarism

“I just want to know why, we, a billion dollar project that paid $10m dollars to develop our layer 2, have another projects Chain ID,” wrote one user.

A series of events erupted in the official Shiba Inu (SHIB) Discord on Mar. 17, when a top-ranked community member, Steve, alleged identical chain IDs between that of the Shibarium layer-2 beta testnet ID and the Rinia testnet ID, an existing blockchain.

“So why is it that it looks like shibarium test net has taken rinia testnet genesis file Changed the name from renia But forgot to change the chain ID Rinia has been live and owned that chain Id since Feb. And was planned in December.”

Steve also alleged that “there’s no way for it to be taken over without shytoshi and kaal [Shiba Inu developers] specifically having coms with him and asking him to reboot (tricking him) so they could take his genesis file and steal his work.” To which Kaal responded:

“Dispelling some FUD ever since we did the Alpha network deployment few chain IDs were picked randomly- 417(Alpha), 517(Staging), 917(pre-pod/beta) and these chain were not registered anywhere at that time, I made a mistake to not recheck when the puppynet network was launched”

Kaal then stated “without getting into any fist fights,” a new version of Shibraium beta network with a new chain ID would be deployed. However, the incident intensified later in the day when Steve raised another allegation, this time regarding the similarity between Shibarium Alpha Test and Mumbai Polygon via a comparison of two screenshots: 

“Shibarium GitHub shows the shibarium alpha test is just a 100% copy of Mumbai polygon.”

At the time of publication, Shiba Inu is down 4.65% over the past 24 hours to $0.00001047 apiece. Cointelegraph has not independently verified the allegations and responses brought by the Shiba community.

Steve’s original post on allegations of plagiarism in Shibarium. Developers have since denied the allegation. Source: Shiba Inu Discord

Leave a Reply

Your email address will not be published. Required fields are marked *