Our use cases are primarily centered around two aspects. We, at Skibble, use Fireblocks as a digital wallet to outsource the transaction processes and manage the complexities associated with blockchain. Additionally, we use it for custodial purposes to manage the crypto assets of our users, while fiat currencies are held in our company bank accounts.

I appreciate several aspects of Fireblocks. The implementations they offer are very clear, and the webhooks are well-constructed. The documentation is comprehensive, and their support, available almost twenty-four seven, is incredibly helpful and responsive. I also admire the range of services they offer, including staking and multi-chain capabilities, which allow us to easily scale our assets.

One area that could be improved is the reconciliation methods. We need to ensure that our accounting aligns with what is displayed in the Fireblocks console, and currently, this process is somewhat manual.

We have been using Fireblocks since 2022, which means we have had it for about two years.

We have encountered a few minor issues, but they are very occasional. Fireblocks has been extremely stable, and it's rare to experience downtime. The status page is very clear and keeps us informed about the status of the services.

The scalability of the product is very good. We have been using Fireblocks for two years, and when we need to scale or update, it's well-built. However, there are occasional challenges with endpoint deprecation, which could be improved.

The customer service is excellent. Support is almost available twenty-four seven. Whenever we experience an issue, they assist us quickly, which is great.

A team of four developers was involved in the integration.

I am not involved in managing pricing, setup costs, or licensing, so I am unclear about these details.

Overall, I would rate Fireblocks an eight and a half to nine. I do not manage our company's partnership with Fireblocks or other commercial agreements, and I prefer to remain anonymous in the review. The overall solution rating is 8.5.

Right now, we at the bank are trying to customize some cryptocurrency. In Peru, at least ten percent of the people here try to invest in Bitcoin, Ethereum, or similar currencies. We try to implement custodial services for these currencies.

The first step is to hold the currency at the bank without creating an exchange, mainly to handle transactions and investments in other changes and to hold that currency. We also create a bot for that currency here at the bank and facilitate transactions like buying and selling Bitcoin and Ethereum.

Here in the bank, we use Fireblocks to create all the transactions, custody of the keys, and the creation of new tokens related to cryptocurrency.

The feature we like the most is the console part since it uses confidential computing. This allows us to hold the private key safely here at the bank. The technology is very easy to use, very cheap, and very secure.

Another valuable feature is the web console, which is very user-friendly and the documentation is clear. The onboarding process is excellent, and the support team is very responsive through Slack.

Currently, we face issues using other technologies and operating systems since the documentation is very restrictive. Here, the bank uses Red Hat, and there's a lack of flexibility to adapt Fireblocks to various customer technologies. The backup process, in particular, is very rigid and can only use specific tools and versions.

We have been working with Fireblocks for at least the last six months.

The stability is very reliable. We only had one minor issue related to a timeout, but overall, there have been no significant problems with the technology.

Fireblocks has enough scalability for our needs. We have a low volume of transactions now, but if we need more capacity, we must notify them in advance as they may need to change system configurations.

The support team is very helpful and responsive. We have a special channel in Slack where they respond to queries, typically within 24 hours, and sometimes even faster. They follow up even for technical issues that may take longer.

We previously had meetings with other providers like BitGo and Paxos. However, Fireblocks' full platform for transactions and custodial services made it the preferred choice.

The onboarding process with Fireblocks was straightforward, mainly due to the clear and detailed documentation.

We initially worked with a technician team from Fireblocks. Although we only had limited hours with them, their support was helpful.

Currently, we have a budget of up to $10,000 for a yearly contract. An issue we face is the limited number of support hours included. We have only fifty hours with technicians, which is insufficient and expensive for additional hours.

We evaluated solutions from BitGo and Paxos, among others, before deciding on Fireblocks.

I would recommend Fireblocks to any organization looking to create its own exchange or custody service for cryptocurrency. It is an excellent choice for creating wallet transactions and holding tokens securely. I'd rate the solution nine out of ten.

Fireblocks is a very complete asset of options. In this regard, everyone was quite pleased with it. There were some difficulties at first, and we also had some confusion, but their support helped us. They even changed one of their manuals to make it easier for others to understand, so that's also interesting. Fireblocks is a complete tool for crypto, which was helpful for us.

We were using PHP, and the solution didn't have much support for it. For example, I needed to check the signature to ensure that it was safe and it was from them. I wasn't sure which key I was supposed to use, and there was no code. I had to guess how to make a code and use a key. If it didn't work, I don't know if the problem was with the code or the key.

I found another person in their forums who also was using PHP. He seemed to have a PHP code, and I got that. I assumed that the code should be working and tried it with the right key. I found it, and it worked.

I first started using Fireblocks a few months ago. I started working in a new place, and we needed a new crypto service. Fireblocks was chosen, and I implemented it in our service.

I haven’t heard about any stability issues with Fireblocks. Recently, we had a case where a transaction responded with the complete status three times for no reason. It didn't affect us very much, but it was strange.

I rate the solution’s stability a nine out of ten.

The solution’s technical support is fine.

Fireblocks was the third financial option I had to implement in our system. I already had some experience, but it was very different, and there was some confusion. For example, they seem to understand that there are many use cases. For some, the user will have their wallet and vault, and it's supposed to work by themselves.

In our case, we wanted everything to be swept into our main wallets. They had a whole section about their recommendations. It felt like it was automatic. Later on, we found out that we had to implement it manually. We implemented it as they suggested, and everything later worked fine.

I would recommend the solution to other users. Fireblocks is a complete solution for handling many crypto-related wallets, deposits, and withdrawals.

Overall, I rate the solution a nine out of ten.

Fireblocks is primarily used for custody. We use it as a custody wallet where we manage all our funds within Fireblocks. Our user-facing interactions are handled through our APIs. We deal with Fireblocks to manage the main vault where our funds are securely structured and segmented. The security is maintained by Fireblocks itself. On our end, we build user-facing APIs that allow users to view their balances within Fireblocks without having to interact directly with Fireblocks. We have multiple use cases for Fireblocks, but most of them are focused on cryptocurrency.

Fireblocks manages everything related to blockchain transactions. We don’t need to handle the provider or the security of the wallet ourselves. The most important factors are the security and stability of their service. Visibility is also crucial; we have that with Fireblocks; we can track what’s happening and what’s not.

We need better visibility into blockchain activities, especially when issues occur. For example, having detailed logs for transactions on the Fireblocks chain would be helpful. A dashboard with such logs would allow us to see directly what happened on the blockchain. We lack this detailed information and often need to provide Fireblocks with specific IDs to trace issues. If Fireblocks could allow clients to trace these issues themselves, it would save time for us and Fireblocks.

Most of the time, we haven’t experienced stability issues with Fireblocks. When issues arise, the main concern is the lack of visibility into blockchain activities. While stability has been consistently good, more detailed visibility would be helpful.

Fireblocks is reliable and handles many security and management aspects, allowing us to focus on other things.

Security is the most important factor. Fireblocks are not inexpensive, but the cost is justified by the security it provides. The second key aspect is stability. Fireblocks handles the infrastructure for wallet management and transactions, which allows us to focus on preparing the necessary hooks and integrations on our end. This setup ensures we can connect and work effectively with Fireblocks while relying on their robust service and infrastructure.

We explored other options previously, primarily due to cost concerns. We found some lower-cost alternatives, but we already have experience with Fireblocks, and they effectively handle our fund management needs. Fireblocks addresses all the issues we had before, and we are satisfied with their service.

Starting with Fireblocks was relatively easy for us. Working with the cosigner API was the most complex part, especially the first time. Everything else was straightforward. Their API is well-documented and user-friendly.

First of all, make sure to sign a solid contract with Fireblocks and understand all their plans and costs. It's important to be aware of the expenses involved. In terms of their service, they are excellent. I recommend them to anyone with a reliable infrastructure for managing wallets, NFTs, or other assets. They provide strong visibility and ensure nothing is missing, with a track record of zero data loss. This is crucial for handling money and funds.

When working with Fireblocks, ensure you understand the technical aspects and how to build your systems accordingly. For example, if you integrate with Fireblocks’ webhooks, you should set up a queue for these events to organize and store them properly before processing. This prevents data duplication. From our experience, we know how to work with them effectively, and we don't face any major issues. We initially had some challenges, but after addressing them and taking action on our end, things have been running smoothly.

From my experience using Fireblocks on the operational and technical sides, I understand their processes well and trust their approach. I can see the specific requirements for transactions and operations. However, it's important to consider that additional layers of security may be needed to ensure continued protection and functionality.

Overall, I rate the solution an eight out of ten.