Ripple’s move to offer its network users more decentralization seems to have gained another ground following the publication of a newly proposed feature aimed at improving XRP Ledger privacy.
One of the Lead Software engineer at Ripple Labs, Inc. Nik Bougalis, has announced the onboarding of a newly proposed spec on the XRP Ledger. As related by the lead C++ software engineer, the newly added feature is dedicated to enhancing the privacy feature on the XRP Ledger.
“The Blinded Tags proposal allows for source and destination tags to be cryptographically scrambled so that they are meaningful only to the source and destination of a transaction,” Nik said.
Nik who was named among the top 100 blockchain and crypto influencers on Twitter in the year 2018, said the development was achieved through a joint task force.
“Although the proposal carries my name, several of my colleagues on the Ripple C++ team contributed heavily. Any mistakes in the spec are, of course, mine.”
While relating the development to the crypto community, Nik dropped a link directing interested users to the Github page of the publication.
Named XLS-9d: Blinded Tags, the newly proposed feature was created on Monday, March 30, 2020.
The XLS-9d: Blinded Tags will prevent attackers from monitoring payment transactions, as well as foil every attempt to segregate a pair of transactions that refer to the same unblinded tag.
Without increasing the time needed to assemble a transaction, XRP Ledger, through the introduction of the proposed XLS-9d: Blinded Tags, will be able to tag blind as a single function call while executing a transaction. The proposal will also grant the network better performance and security.
The proposal assumes no less than four additional features to the XRP Ledger, allowing users to enjoy varieties of intriguing new features.
The proposal lets users specify the standard they want. The blinded tag feature is designed in a way that is purposeful to the sender and receiver alone, but random to every other person.
To enjoy the new feature (blinded tags) during every transaction, individuals need to enable the feature set by accessing AccountSet transaction in their account, as revealed in the Github page.
