Fireblocks Digital Assets Platform
Advanced automation has improved AML workflows and secures multi-party crypto transactions
What is our primary use case?
I have not switched from Fireblocks, but I am working on another project, so I do not require it right now. Fireblocks SDK was an MPC-based crypto wallet that was custodial, functioning as a multi-part computing wallet. It was mostly required in centralized exchanges or for building and maintaining user crypto assets. It provided security and helped developers and companies set up transaction policies and manage user transactions through the AML process, onboard new customers, and create wallet accounts for them. For that reason, the MPC-based wallet is useful.
A second option was that MPC provided multi-part signing capabilities, meaning multiple parties can contribute to transactions and approve or reject them based on signing their transactions or providing signed transactions for approving user transactions. This can be anything from minting to redeeming.
What is most valuable?
I used Fireblocks for automated asset settlement workflows, and automation was present through AML processing. It provided an option where I could easily automate my AML process through their platform without needing to configure or do anything on my own system separately. The auto-fueling option was available, and I could easily create a transaction policy on that platform. Whenever a transaction was run or triggered through Fireblocks SDK, it would first check my policy and then trigger the transaction on-chain.
I assess the impact of Fireblocks' policy engine on my compliance efforts as it provides built-in features, such as AML processing, which I can manage easily by enabling their system. Another option was the auto-fueling feature. If I wanted to do a transaction from the admin side to the user side, I could easily auto-fill the transactions by gas fee. Setting up policies for different transactions, including transfer, mint, or redeem, was easily achievable. It provided me options on how I wanted to carry out the transaction, what wallets I wanted to whitelist or blacklist, which I could do easily. On user wallets, if I created a user wallet, I could maintain multiple crypto assets including Bitcoin, Solana, Ethereum, and Polygon. It is popular among blockchain projects. MPC is mostly used for maintaining stablecoins or liquidity of custodials.
I measure the effectiveness of Fireblocks' end-to-end encryption in securing asset transfers by doing two things: one is off-chain verification on my platform, checking the user balance and gas fees, how much it will cost, and signing transactions, and how the transactions have been signed. On Fireblocks SDK, I am doing the transaction policy work, setting up all transactions and how they should be run. For that, I have set the smart contracts. On the smart contract, I have done some KYC enabling on-chain. If any transaction runs, I check which method or transaction method of the smart contract will be allowed and how, and which address has been whitelisted to allow the transaction to run. It can be an admin account, a minter account, or a redeemer account. I have set different role accounts for access control, and from there, the transaction is run.
What needs improvement?
I think one feature that Fireblocks could add to make the product better is AI automation features. AI automation processes are working extensively now, and if they provided features for verifying whether a transaction is valid or not based on AML processing or transaction policy, it would be beneficial. Auditing and compliance are very important, and crypto law has become very strict based on different countries. If they improve that and the automation is handled by the AI system, implementing it in their platform would make it much easier to manage. Because currently, I also need to maintain the AML process manually on my system. Though Fireblocks SDK manages it through third-party systems such as Chainalysis, I still need to verify it again sometimes, ensuring that I follow all the rules and regulations of the AML process or KYC onboarding process.
For how long have I used the solution?
I stopped using it in the previous year, around last summer.
What do I think about the stability of the solution?
I found some problems when working with Fireblocks due to the full control they do not provide. When some transactions I was running failed, I needed to re-trigger the transaction again, but sometimes I was not able to track which transaction had failed. In that case, the issue was occurring sometimes, but now Fireblocks has resolved that issue. Previously, it was appearing, and they have provided a status update. If any transaction is running and network congestion is too high on-chain, such as on the Ethereum blockchain, they immediately trigger an alert that balance is not sufficient to run the transaction on-chain, and I need to refill the gas fee. This has been handled by Fireblocks now, and this is the only issue I have faced.
How are customer service and support?
My customer service rating is 4.
Secure custody has transformed daily trading operations and now manages all crypto workflows
What is our primary use case?
Fireblocks is my main solution for all of our custody of funds, for trading, for migration, and for every process in our company because we are a blockchain company with a huge amount of funds, and a lot of the processes, trading, and everything is handled through Fireblocks.
A specific example of how Fireblocks is used in a day-to-day scenario at my company is that whenever we need to send funds to any exchange, or receive funds, or make any payments in crypto, we use Fireblocks on a daily basis for all of those.
What is most valuable?
The best features Fireblocks offers include security features, whitelisting processes, the ability to create many wallets and name those wallets, and the capability to whitelist specific dApps which you can connect to, and broadly specify addresses to which you want to send the funds, helping us manage our operations.
These security features and whitelisting processes help my team manage our operations more effectively because they reduce the risk of sending funds to an incorrect address, and they make the funds more secure since we only whitelist addresses that we know, therefore nobody can hack the wallet and withdraw to any wallet as it will not let you withdraw.
Fireblocks has positively impacted my organization by making a huge impact since it has enabled our chain in Fireblocks and integrated our Chiliz chain, giving us immense exposure and immense help in everyday managing operations.
Fireblocks has saved us a huge amount of time, and while it is hard to quantify the time it has saved, it has certainly reduced manual labor, automated tasks, and given us peace of mind when everything is so secure and systematically organized.
What needs improvement?
Fireblocks already has a pipeline of new features to improve, such as migrating from one chain to another instantly, which they are already working on.
For how long have I used the solution?
I have been using Fireblocks for four years.
What do I think about the stability of the solution?
Fireblocks is stable.
What do I think about the scalability of the solution?
Fireblocks's scalability is great, scoring one hundred out of one hundred.
How are customer service and support?
Fireblocks customer support is great, as they reply very fast and immediately.
Which solution did I use previously and why did I switch?
I previously used a different solution before Fireblocks, which was Cobo Custody.
I switched from Cobo Custody to Fireblocks because Fireblocks is better and provides more features than Cobo Custody.
Which other solutions did I evaluate?
Before choosing Fireblocks, I evaluated other options including BitGo Custody.
What other advice do I have?
My advice to others looking into using Fireblocks is to not create so many wallets; it is better to only create a few wallets, properly name them, and instead, avoid whitelisting many addresses. If there is an address for a one-time transfer, use only a one-time address for that transfer to save a lot of time and effort. I would rate my overall experience with Fireblocks as a nine out of ten.
Secure treasury management has transformed our workflows and delivers faster institutional settlements
What is our primary use case?
Fireblocks keeps all of our assets in digitally secure wallets. At Chiliz, my main use case is that it provides an institutional-grade risk framework for our corporate treasury, especially as I am managing millions of funds in digital custody. I use Fireblocks for high-stakes treasury management, ecosystem-wide network updates, and to keep all of our assets safe and secure.
Fireblocks helps us in many ways in our day-to-day operations. It is our primary operational command center for managing liquidity across 70+ global exchanges where our token is listed. A perfect example is that during our recent $1 billion worth of 70+ tokens migration, instead of manually managing fragmented wallets, I used the policy engine to automate multi-signature approval for high-volume transfers. This allowed our team to deploy assets to institutional partners in minutes rather than hours, all while maintaining a zero-trust security architecture that protected our millions of dollars in treasury from any single point of failure.
Fireblocks is essentially the operating system for our entire Web3 ecosystem. It fits into our workflows as the final trust layer for every single transaction. Whether we are minting new tokens or managing migrations across 70+ global exchanges, Fireblocks is what allows me to sleep at night. It is a bridge that connects our institutional-grade security requirements with the fast-moving world of DeFi and fan token utility.
What is most valuable?
I think the best feature Fireblocks offers is the MPC. It is a multi-party computational custody feature that allows you to move away from risky manual hardware wallets and physical seed phrases to a cloud-native secure environment for managing assets. Then there are the policy engines, Fireblocks' own network, its DeFi API, Web3 engine, and audit-ready reporting we can download in minutes.
The policy engine arguably makes my job easier and safer as it allows me to architect complex multi-tier approval workflows that require specific quorum for high-value transfers while automating micro-transactions, effectively removing any single point of failures.
Fireblocks has positively transformed our organization specifically in three key areas. Firstly, operational velocity: during our technical upgrades and managing blockchain rollouts, everything is very fast. Secondly, risk mitigation and security: instead of managing through hardware wallets, we keep secure custody in their MPC architecture. Thirdly, scalability for our ecosystem growth: it has provided the institutional-grade infrastructure needed to scale our B2B partnership. We were able to launch over 50 fan tokens and manage complex network migrations with the confidence that our underlying treasury was secure and compliant with global standards.
What needs improvement?
I think one area Fireblocks can improve is the cost barrier; the annual licensing fees are quite high for institutions and others. They need to reduce it to make it more accessible for more users.
Regarding DeFi and smart contract interactions, interacting with new or obscure DeFi protocols via WalletConnect can sometimes be clunky, often requiring trial and error or manual workarounds. The smart contract UX could be improved; while core transfers are flawless, the interface for interacting with complex and non-standard contracts could be more streamlined for operational speed. This is an area I think Fireblocks can enhance.
For how long have I used the solution?
I have been using Fireblocks for the last three years.
What do I think about the stability of the solution?
Fireblocks is very stable.
Which solution did I use previously and why did I switch?
Previously, we used Cobo Custody and switched to Fireblocks because it is better and provides everything we need.
What was our ROI?
We have seen a return on investment, significantly through time savings and risk reduction.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is acceptable; while the price is a bit high, overall, it was manageable.
Which other solutions did I evaluate?
Before choosing Fireblocks, we evaluated BitGo and Ledger Enterprise.
What other advice do I have?
Previously, we managed our assets manually, which led to a very big mismatch in the funds. While the documents showed 1.5 million, in actuality, the amount was much less, leading to a 1.5 million mismatch that required digging through transactions one by one to resolve. Through Fireblocks, it has become so easy for us; reports are auto-ready, we can download them in a second and identify any discrepancies within a moment. Transaction processing times have increased, with signature generations for our MPC wallets now 8x faster, eliminating any single point of failures.
My advice for others looking into using Fireblocks is to prioritize mastering the policy engine early to balance institutional-grade security with the operational speed needed for global exchange settlements. I would rate my overall experience with Fireblocks an 8 out of 10.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Essential Treasury Security: MPC Wallets and a Powerful Policy Engine
Security and ease of mind built into the system
Comprehensive documentation and responsive support simplify the integration process
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
We have been using Fireblocks since 2022, which means we have had it for about two years.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How are customer service and support?
The customer service is excellent. Support is almost available twenty-four seven. Whenever we experience an issue, they assist us quickly, which is great.
What about the implementation team?
A team of four developers was involved in the integration.
What's my experience with pricing, setup cost, and licensing?
I am not involved in managing pricing, setup costs, or licensing, so I am unclear about these details.
What other advice do I have?
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.