Safle · Web3 wallet platform
Verified resultsExtending a Web3 wallet team across product engineering, QA and DevOps
DevX operated alongside Safle’s internal team across React development, wallet functionality, QA, release support, CI/CD, infrastructure and technical handover.
- Web3 Product Engineering & Extended Delivery Team
- React
- JavaScript
- Web3
- Wallet UX
- QA
- CI/CD
- Kubernetes
- Jenkins
- Devtron
- IBM Cloud
- Technical Documentation
More product scope required more than frontend capacity
Safle was expanding a Web3 wallet platform and needed additional engineering capacity to move product work forward while improving the reliability of releases.
The requirement covered more than interface implementation. Wallet behaviour, browser compatibility, test coverage, CI/CD, cloud infrastructure, documentation and release coordination all affected the team’s ability to deliver safely.
DevX joined the engagement as an extension of the existing Safle organisation rather than claiming ownership of the entire platform.
The engineering decision: extend the existing team across bounded delivery workstreams
Safle retained ownership of the platform and roadmap, while DevX embedded into the existing team across assigned React and wallet work, QA, release support, DevOps and documentation.
The engagement kept contribution boundaries explicit and paired delivery support with a structured technical handover instead of presenting DevX as the builder of the entire platform.
Frontend and wallet product work
- React frontend development and conversion of interface work into reusable JSX components.
- Wallet creation, import, recovery and management flows.
- Safle ID and wallet-related functionality.
- Asset send and receive journeys.
- Network, token, transaction and gas-fee functionality.
- QR-code-based wallet interactions.
- NFT listing, detail, send and receive flows.
- Keyless wallet integration work.
- Browser-extension and DApp connection/disconnection flows.
- API, currency-data, registration and migration-related integrations.
- Browser compatibility investigation and production bug fixing.
QA, release and stabilization
- Regression testing and product stabilization.
- Tracked testing and release work across multiple WebApp releases.
- Sprint planning, review and release coordination.
- Issue investigation and handover preparation.
- Documented QA effort alongside engineering delivery.
CI/CD, infrastructure and technical documentation
- CI/CD implementation and release support.
- DevOps work involving Kubernetes, Jenkins and Devtron.
- IBM Cloud and infrastructure-related investigation.
- Monitoring, ingress, cluster and service documentation.
- Technical documentation for product and engineering workstreams.
- Structured technical handover back to Safle.
A broader delivery capability followed by a structured handover
Across the engagement, DevX contributed to multiple product and delivery workstreams while Safle retained ownership of its platform and roadmap.
The documented collaboration extended from January through August 2022, followed by technical handover activity in September 2022. Safle received product-development support together with QA, release, DevOps and documentation capacity.
The case study does not claim that DevX built the entire Safle product, all backend services, blockchain infrastructure or smart contracts. It also does not attach business outcomes to Jira ticket volume.
Engineering dossier
Delivery and outcomes
Delivered outcomes
- Extended delivery capacity across product engineering, QA and DevOps
- Additional wallet, asset, NFT and Keyless workstreams
- Support for multiple tracked releases
- CI/CD, infrastructure and technical-documentation contribution
- Structured technical handover in September 2022
Verified results
Evidence and context
Verified metrics
- Continuous collaboration, January–August 2022
- 8 months
- Documented QA effort in May 2022
- 55 hours
- Documented DevOps effort in May 2022
- 10 hours
- Technical handover completed
- Sep 2022
Measurement record
Documented engineering engagement
- Metric
- Documented engineering engagement
- Starting point
- The retained service agreement begins in January 2022 and defines DevX as an extended contributor to the existing Safle team.
- Outcome
- Records support continuous collaboration through August 2022, 55 QA hours and 10 DevOps hours in May, and technical handover activity in September 2022.
- Measurement method
- Dated agreements, invoices, weekly reports, release spreadsheets, meeting records, Jira history, and handover material were cross-checked.
- Measurement period
- January–September 2022.
- Source
- Service agreements, invoices, Jira, weekly reports, release spreadsheets, meeting records, and handover documentation retained internally.
- Attribution boundary
- This verifies the engagement period and recorded DevX workstreams; it does not claim ownership of the full platform or platform-wide business, security, or performance outcomes.
Verified Results. Service agreements, project trackers, Jira history, release spreadsheets, technical documentation, meeting records, invoices and handover activity support the engagement period and described workstreams.
The live site may have changed since this engagement. This dossier describes the approved delivery scope and evidence available for the project period.
Unapproved media and operational details outside the approved scope are omitted.
Relevant services
Related engineering dossiers
- Verified results
Scaling HTML5 campaign production for Craft Worldwide
DevX translated supplied campaign creative into production-ready HTML5 and static advertising assets across multiple formats, specifications and localization requirements.
Read case study - Selected work · Documented project
Rebuilding a legacy ecommerce store without losing the customer experience
DevX replaced a fragile WooCommerce foundation with a leaner, supportable implementation while preserving the store’s familiar visual direction and critical sales flows.
Read case study