DATA SHEET DS-02 · WEB3 DEVELOPMENTREV. 2026-A

Web3 development, proven in live projects

For us, Web3 is not a topic for the future but day-to-day work. We have contributed to projects that run in production: USDFI, Arrowtrade and unCoded. For your project we build the interface through which users connect their wallet and approve transactions, and the interfaces that bring blockchain data into your application.

Already have a development team? Then we reinforce it or take on a clearly defined package. In the initial consultation we look at the code, not at slides.

Discuss a Web3 project

Projects we have contributed to.

We show work rather than promises: three projects that run in production and on which we worked as a development partner. You will deliberately not find figures on users or volume here (those numbers belong to the projects, not to us). What we can show: the code, our contribution, the conversation.

RECORD 002

USDFI

DeFi protocol: stablecoin, decentralised exchange, lending.

A protocol that combines a stablecoin, a DEX and lending. Aureum worked on the project's web development.

RECORD 003

Arrowtrade

Swiss provider of automated trading solutions.

Trading software, Web3 and DeFi development, nodes and data feeds. We contributed to the development of the platform. The project turned into a partnership: today we develop websites, software and AI together.

RECORD 004

unCoded

Non-custodial crypto trading bot.

The customer keeps keys and account; built to be machine-readable with an MCP server, OpenAPI and llms.txt. Aureum was involved as a development partner.

Projects we contributed to as a development partner.

Which of these fits your project is best discussed directly.

All projects

What should your application be able to do?

It does not have to be a large project. A dashboard that makes blockchain data readable, a single wallet action or importing data into your software: any of these is a sensible first job.

Your dApp needs an interface that users understand.

We build frontends for DeFi protocols and decentralised applications: wallet connection, live data from the chain, understandable interfaces for complex processes. Users see which wallet is connected, what they are approving right now and whether the transaction has gone through or failed.

You need blockchain data in your own software.

We connect blockchain data with conventional systems: indexing, APIs, reporting. The events of a smart contract become an interface that your dashboard or reporting can work with. Properly documented.

You have taken over a project and want to know what holds up.

We read the concept and the code and tell you honestly what holds up and what does not. Afterwards you will know whether a targeted extension is enough or whether the foundations need work first, and you will have a proposal for the next steps on the table.

Before the first conversation, our free Web3 tools can help. The blockchain suitability check clarifies whether your project needs a blockchain at all; the MiCA check classifies a planned token under the EU regulation.

There are more for the development itself: the vesting planner calculates release schedules for tokens, the Merkle generator builds allowlists in the browser. The NFT metadata checker shows whether NFT metadata appears correctly on marketplaces.

How does blockchain data get into your application?

Your dashboard is meant to show the movements of a smart contract or to bring holdings together for a report. For that we first define where the data comes from: which network, which contract address, which events.

Then we build the path. An indexer reads the events from the blockchain and stores them so that they can be queried. Your application fetches them through an API. If a direct query is enough for the task, we leave the indexer out (shorter is better).

The free node planner works out whether an RPC provider is enough or you need your own node, based on storage, RAM and synchronisation per client. The selector calculator shows which function hides behind a selector in the data.

The index can lag a little behind the chain. In the diagram that is the moment when block N already exists and the application still shows the state from block N−1. That is why we put the data state, with a timestamp, into the interface. Your team can then see at a glance whether only the latest update is missing or a source has failed.

THE DATA PATHBLOCKCHAININDEX ANDINTERFACEAPPEXAMPLE: THE SAME MOMENT AT THREE POINTSBLOCK N EXISTSBLOCK N PROCESSINGBLOCK N−1 WITHTIMESTAMPTHE DATA PATHBLOCKCHAININDEX AND INTERFACEAPPEXAMPLE: THE SAME MOMENT AT THREEPOINTSBLOCK N EXISTSBLOCK N PROCESSINGBLOCK N−1 WITHTIMESTAMP
FIG. 1 · DATA PATH TO THE APPLICATION

Users should know what they are approving.

Connecting the wallet is one thing. Nothing is triggered until the user signs in their wallet. Before that, the application shows what they are approving: where it is going, how much and on which network.

After signing, the application stays on the case. For us, “sent” does not mean “done”: the interface distinguishes between a transaction that is still waiting for its block and a result that has been verified. If the user declined in the wallet or the execution failed, that is shown too, in words they understand.

Two free tools show what this looks like on a small scale: the calldata decoder translates a transaction into plain language, the Ethereum address checker spots typing errors and look-alike recipients.

FROM ACTION TO RESULTACTIONPREPARESIGNATURE IN THEWALLETSENT,WAITING FORBLOCKCHECK RESULTTWO POSSIBLE RESULTSEXECUTION SUCCEEDEDEXECUTION FAILEDFROM ACTION TO RESULTPREPARE ACTIONSIGNATURE IN THE WALLETSENT, WAITING FORBLOCKCHECK RESULTTWO POSSIBLE RESULTSEXECUTION SUCCEEDEDEXECUTIONFAILED
FIG. 2 · TRANSACTION AND RESULTDASHED = WAITING TIME · GOLD = USER'S APPROVAL

From the first use case to handover.

We start with one tangible piece that you can try out and sign off. How fast it goes also depends on access and on how quickly we get your feedback on the content. Further functions follow afterwards, each with its own scope.

  1. Understand the task and the existing setup

    You show us what the user is meant to do. We read the existing interfaces and write down what we will build and how you will sign off the result.

  2. Prototype in the test environment

    We build the process in a test environment first. You click through the interface; we check whether the data is right and what happens in the error cases.

  3. Refine and approve

    We work through your feedback and document the tests. If smart contracts are new or changed, we plan the external audit as a separate item. Who approves the launch is settled beforehand.

  4. Hand over and operate

    At the end you receive the documentation and a briefing. With your team we settle who manages access, who handles faults and who commissions later changes. What we continue to look after is set out in black and white in the quote.

What does the application need once it is live?

After launch, interfaces and dependencies change; in Web3 that is the normal case. That is why we settle during the project what is monitored and who reacts when something fails. For data imports this means: restarting after a fault and backfilling the gap are part of the plan.

In the quote, development and ongoing services are listed separately. Depending on the set-up, hosting and data provider fees come on top. We list transaction fees as a separate item: they depend on the network and fluctuate with its load. That way you know before the start what to expect in operation, and not only what the development costs.

The free gas calculator works out in advance roughly what a transaction costs on which network.

How Aureum and Arrowtrade work together.

Specification

DATA SHEET DS-02 · WEB3 DEVELOPMENT

Areas
DEFI · DAPPS · INTERFACES · BACKENDS
Our work
USDFI · ARROWTRADE · UNCODED · AS DEVELOPMENT PARTNER
Reading
BLOCKCHAIN DATA · INDEXING · APIS FOR EXISTING SYSTEMS
Writing
WALLET CONNECTION · TRANSACTIONS UP TO THE VERIFIED RESULT
Getting started
ONE FUNCTION · PROTOTYPE IN THE TEST ENVIRONMENT
Way of working
CODE REVIEW · CLEAN DOCUMENTATION
With your team
AS REINFORCEMENT OR WITH OUR OWN CLEARLY DEFINED PACKAGE
Collaboration
AGREEMENTS THROUGH AUREUM · DEVELOPMENT WITH ARROWTRADE
Location
RODEWISCH (SAXONY) · PROJECTS NATIONWIDE
Quote (Angebot)
IN WRITING BEFORE WE START · DEVELOPMENT AND RUNNING COSTS SEPARATE
Initial consultation
FREE · LOOKING AT THE CODE, NOT AT SLIDES

Prices

€90 per hour plus VAT (MwSt.). That is the standard hourly rate; for some work, for example on servers or networks, a higher rate may apply, and it is stated in the written quote (Angebot). We charge for the time we spend, rounded up to the next quarter of an hour. Travel from €20 plus VAT. If you prefer, a monthly flat rate instead of hourly billing. The initial consultation is free, by phone or at your premises; we do not charge for the travel either.

Questions & answers

Common questions, answered briefly.

What experience does Aureum have with Web3 and blockchain?

We have contributed to Web3 projects that are in live use: USDFI, a DeFi protocol with a stablecoin, decentralised exchange and lending, to which Aureum contributed web development; the Swiss trading platform Arrowtrade; and unCoded, a non-custodial trading bot. We can show you the details when we talk, with the partners' approval.

Do you work with our development team?

Yes, in fact that is the usual arrangement. We reinforce teams on frontend, backend or interfaces, or we take on a clearly defined package on our own. Beforehand we agree with you who gets access to the repository, who reviews changes and who approves a release. That way both teams know when something is ready for acceptance.

Do you also develop smart contracts?

We connect existing smart contracts, build clearly scoped prototypes and review existing code. If a new or changed contract is to go live, we build the external audit into the plan from the start. The reason is simple: a small change to the contract can affect the whole application.

Do we actually need a blockchain for our project?

Not always. It makes sense if your application is to work with an existing network, or if several parties should be able to verify the same state for themselves. If everything is controlled by one party, a conventional database is usually enough, and it is easier to run. If the conventional solution fits better, we will tell you so in the initial consultation.

Do we need to have chosen a network and a wallet already?

No. Tell us what your users are meant to do and who they are. From that we can work out which networks and wallets are suitable and what they cost. If your project already runs on a particular network, we build on that. In the quote (Angebot), networks and integrations are named explicitly.

Can we keep our existing website or software?

Usually yes. We typically attach an analysis of blockchain data as a separate module to what you already have. For wallet actions, the user guidance must also fit the existing system, so we look at your interface more closely. How we otherwise design and build web interfaces is described under web design and web development.

Why does our application sometimes show an older state than the blockchain?

Because there are several steps between a new block and what you see: the indexer processes the events, a cache holds responses ready, and the interface reloads at intervals. This is normal. That is why we show clearly how current the data is, and if something fails, your team can see which source is stuck.

Is a transaction done as soon as the user has confirmed it in the wallet?

No. By confirming, the user signs and sends the transaction. After that it waits for a block, and during execution it can still fail. Our interfaces therefore only report success once the result has been verified. The process behind this is described in the Ethereum documentation on transactions.

What does Web3 development at Aureum cost?

That depends on the scope. Before we start you receive a written quote, either by time spent or as a clearly defined package. Running costs such as hosting and data providers are listed separately in it. The initial consultation is free; the hourly rate and billing are described under prices and billing.

Where does your work stop?

In three places. Our code review tells you what we found in the agreed part and what needs fixing; the independent audit before a live launch is done by a specialist audit firm. Legal questions, for example about a token model, belong with a lawyer. And we build technology: whether a token or a business model is commercially viable is not something we assess.

Contact

Let's talk about your Web3 project.

Tell us in two sentences what your application should do and where you stand. In the initial consultation we look at it together, directly in the code if you like. It costs nothing and does not commit you to anything.

+49 3744 4399760Mon–Fri 8:00–17:00
CallEnquire about a Web3 project

PARTS LIST · SHEET 1/1

What this page is made of

Values measured at build time. With JavaScript, your browser measures them again live.

ITEMPARTTYPESIZE
01index.htmlDocument≈ 29 kB
02styles.cssStylesheet≈ 20 kB
03scripts.jsScript≈ 13 kB
04archivo-variable.woff2Font≈ 58 kB
05ibm-plex-mono.woff2Font≈ 30 kB
06favicon.svgImage< 1 kB

Advertising or analytics cookies: none. Without your consent, the page loads nothing from third-party servers apart from Cloudflare, our delivery service. Fonts, scripts and images are hosted by us. That is how we build your IT, too.

OUTSIDE OFFICE HOURS

Feel free to call anyway

Our regular office hours are Monday to Friday, 8:00–17:00.

In the evening and at weekends the number is forwarded to us, and often someone will pick up. We cannot promise that, though.

If nobody answers, leave a short message on the voicemail: your name, your number and what it is about. We will call back as soon as we can, on the next working day at the latest.

The call costs nothing. If someone has to start work straight away outside office hours, the surcharge in the price list applies.

Call now+49 3744 4399760

Prefer to write? Use the contact form or e-mail [email protected]. We will read it on the next working day.

DIAGNOSIS · AT-K2

What do you need help with?

↵ SELECTESC CLOSECALL: +49 3744 4399760

Custom settings

Which services may load?

Strictly necessary

The choice you make here and your settings for colour scheme and motion. These are kept as small entries on your device and are never sent to a server. They are needed for the site to work and therefore cannot be switched off.