Ironblocks
OVERVIEW
Ironblocks provides modular Web3 security solutions for DeFi protocols, with a focus on protecting smart contracts and firewall management.
ROLE
UX UI solo designer, creative lead

Goal
The goal of this project was to streamline the process of uploading and managing smart contracts within the Ironblocks platform, while enabling seamless configuration and connection to the firewall.
Integrating smart contracts within the platform brings complexity, from technological barriers such as the need for precise configuration for multiple contracts, and a transaction signature using
digital wallet.
Challenge
DISCOVER
Competitor Analysis
In the Web3 ecosystem, security remains a critical concern. In 2023 alone, over $3.8 billion was lost due to security breaches and smart contract vulnerabilities in the DeFi space. Many protocols lack robust solutions for real-time defence, which has led to increasing demand for services like Ironblocks.

DISCOVER
User Research
Objective
We conducted qualitative research by interviewing protocol owners. The goal was to understand their experiences, expectations and needs within the Web3 security ecosystem. This research helped us better align Ironblocks’ offerings with market needs and reduce friction in the smart contract onboarding and firewall management process.
Key Findings


DEFINE
Target Audience
The "DeFi Protocol" persona represents decentralized finance platforms of various scales, managing some user bases and transaction volumes. These protocols are focused on user trust, business continuity, and maintaining security.

DEFINE
User Journey Map
Identifying ux issues by mapping essential steps for integration.

DEFINE
Featured User-Flow
To lower friction within the user flow, I mapped out mandatory versus optional configurations. This approach simplified the flow by reducing unnecessary steps and providing clear guidance on which actions were essential versus optional.

IDEATE
Wireframing
As with many other security & developers tools acting across the web3, the first design of this flow allows you to select a chain and then paste the contract addresses.

Design system & Documentation
By studying design systems like Material Design by Google or Atlassian’s design guidelines, I learned how to structure and organize my own design system. For example, how to categorize components, establish design tokens (like colors, spacing, and typography), establish Documentation Practices, and create a consistent UI across multiple products.

TEST
User Testing
As a result of talking with users and gaining feedback, I have come to the conclusion that some changes should be made to improve user experience.

TEST
Behavioural Pivot
In the original flow, users could paste single or multiple contract addresses into a modal. However, as we scaled support for more advanced checks, like firewall compatibility, ABI issues, and policy configurations, the modal format became limiting.
Before:
Key Pain Points Identified:
-
Too much information for a modal UI — As the complexity of contract setup increased, the modal became an overwhelming experience.
-
Validation and firewall compatibility checks were separated, forcing users to jump between stages
-
Lacked clarity when troubleshooting errors across multiple contracts.
To address these issues, I introduced a CSV upload feature. Users can now upload a spreadsheet containing multiple contracts and see them presented in a dedicated table view, with all relevant metadata, validation errors, and firewall readiness shown in one place.
By moving to a dedicated screen, I gave users the space and control they needed to manage complexity, without sacrificing validation or visibility.
After:

Address Book
The Address Book (from the side menu) contains addresses for uploaded smart contracts and other addresses, such as policies and other deployments.

Uploading Contracts using CSV file
Instead of manually pasting the addresses, users can upload a file containing all the addresses they wish to add. On the right side of the screen are instructions for new users.

Firewall adapted contracts
A list of addresses is displayed after the file has been uploaded, including important information about the firewall's suitability. In the absence of offline firewall configuration, contracts cannot be protected, so the user can re-upload, delete, or continue without connecting to the firewall.

Add policies
After being uploaded and monitored, a list of available policies is displayed, including open-source and subscription to showcase security options.

Transaction Page
After being uploaded and monitored, a list of the contracts transactions is displayed, including active and testing environments.

Transaction Details
The user can view the transaction details and manage the security layers including policies and system detectors that was activated.

Feedback & Recommendations

LOCATION
Tel Aviv, Israel
SOCIAL
Tel. 054-567-3099
© 2025 by Noy Avrahami