DEV Community

BiasGoose for RippleX Developers

Posted on • Updated on

Peersyst Technology AMA

In our third AMA (Ask Me Anything) of the year, I spoke with @Ferran from Peersyst Technology to discuss his background developing products on blockchain, why he chose to build Peersyst on the XRP Ledger and how it connects to projects like XUMM Wallet.

Check out the full recap below, and head to for updates on how to join the next AMA!

BiasGoose: Hi @developers! Join me in welcoming @Ferran of Peersyst Technology to our AMA. Today we will be talking about his background, products and vision for the future!

Ferran, please introduce yourself and your project.

Ferran: Hi @BiasGoose it's a pleasure to be here and thanks for hosting us!

Also, I want to say ‘hi’ to all the XRPL community.

My name is Ferran Prat, I'm the CEO of Peersyst Technology, a company based in Barcelona, Spain! We have spent the last 6 years developing blockchain products with different protocols, and we are right now really focused on contributing to XRPL!

We are working in many directions to bring our knowledge to the community, but mainly today we want to talk about XRP Stamp, a product we are launching this week, both on mainnet and a testnet on top of the XRP Ledger! 👉

BiasGoose: Amazing! Quite a fresh product for us to hear about. Can you tell us more about XRP Stamp?

Ferran: Sure! XRP Stamp is a white-label solution for a product that is very useful in any ecosystem and resolves many use cases, especially on the business side.

The solution is about data notarization, meaning that allows you to register any type of data on the XRP Ledger in a JSON format. This data is obviously immutable, stored decentralized on the ledger, and transparent and available to check by anyone, anytime.

The interesting part is when you are mixing this up with IPFS. Apart from metadata stored in a transaction, we can also store document hashes, stored on IPFS. These documents are then reviewable and available to get, but the most important part is we register their integrity. The IPFS hash or SHA hash is unique to its content at the moment of registering it. So, any content registered at a given time becomes true and immutable for everyone who checks that.

Actually, NFTs work in a very similar way, storing an image attached to a token.

In this case, we are storing more information, such as metadata, document hashes and links. All this information goes to a registered account that we take as the source of truth, and it becomes the register for a use case.

Let's put a simple example. Say we want to certify the land registry of a country. We can use this solution to issue valid certificates. The receiving account is the ’official land register’ for the country. The sender account identifies the ‘official emissor,’ such as the government. All the information becomes public, available and transparent to anyone, so you can demonstrate you own that property.

It's just an example, but I hope it shows the usability of the product!

BiasGoose: Awesome, this is a great introduction! Much appreciated. Your product looks very interesting. Can you tell us more about the team behind XRP Stamp? What is their background as well as yours?

Ferran: Sure, @BiasGoose.

Most of our team comes from UPC University in Barcelona. All of us have a computer engineering background, and we had the chance to start working on and developing crypto solutions in 2016-2017. During this time, we had the chance to develop more than 30 projects right now delivered between some blockchain protocols and private clients.

During the last few years, we have been contributing mainly to a blockchain that also was made with built-in features—so we have a good experience playing with the tools that the protocol gives to solve the use cases on top of that. That's why XRPL becomes really useful and familiar to us and one of the reasons we decided to start contributing actively here!

Most of our info is also available on our website——in the About Us section if you want to find out more!

BiasGoose: Yes, here is the link for those looking. Ferran, what made your team choose the XRPL for this particular product?

Ferran: The main reason is that we were working on a couple of projects that needed a solution related to that. They all had very related use cases with all the XRPL functionalities, and we needed a solution like that to cover that part.

So, we decided to build this white label, available for the entire community, to use for this concrete purpose but at the same time made it open-source for the rest of the XRPL devs.

BiasGoose: What is the difference between pointing an XLS-20 to an IPFS file (instead of an image) and the method you’re providing? Will you use the XLS-20 standard?

Ferran: XLS-20 could also be a good approach to that. The main difference is that XLS-20 is storing this information in an asset that can be transferred, sold, etc., and our system is saving all these records in a destination account that is common to all the stamps. So, it becomes the ‘official’ register and source of truth.

You can probably achieve a similar solution by making an NFT non-transferable with the flag.

BiasGoose: So are you recording the stamp in the domain field (19d, I believe), or can you explain what method you’re using? Then, tell us some of the technical hurdles your team went through to deploy this product.

Ferran: The methodology we are using is explained on the product landing page. It shows how to create an XRP Stamp, and it's available to test on mainnet and testnet, connecting XUMM Wallet 📱. You can find all the details on 👉

This question is really interesting @BiasGoose! In general, all the documentation is really good, so it’s easy and fast to implement solutions on top of that.

The main problem we found related to the last part is a particular feature in the XUMM Wallet. We wanted to maximize the user experience of the application, especially for tests and demos.

This application is shown to many people, most of them non-technical, and the idea is they can test it themselves for free and fast. That's why we decided to use XUMM.

The feature we missed is that we could not know if the user was logged on mainnet or testnet. The idea is that if you are on the application and you change the XUMM connection, you are redirected to testnet to facilitate transactions. But from XUMM, we could not find how to detect that, so now the user has to go to settings > advanced > node and change it manually. On the app side, it’s important to access the right link at

BiasGoose: That's awesome! Thank you so much Ferran for talking to us today, we really appreciate it 🫂

To find more about the project go to: and follow Peersyst on Twitter @peersyst.

Top comments (0)