Front End

Our front end team has been busy with building our landing page for the platform. Now they are working on the ETO forms which companies will fill in to sign up to get listed on Neufund. This also includes a redesign of the dashboard for investors and companies to provide users with more extensive information. Once that is finalized the ETO forms can get merged with the rest of our platform.

Our lead developer Krzysztof Kaczor wrote a blog post about Squeezing maximum type safety out of Typescript with TypeStrict. His article made it into the Typescript Newsletter.

Back End

Our back end developers are also working on the ETO listing page. They’ve been creating a database with a connection to the Ethereum network as a wrapper. The ETO book building process is ready for the back end and the ETO listing is even already completed in the back end. They also created an ETO listing back-office interface from which we can asses applicants.

They’ve also put up an IPFS integration to save data. IPFS is a decentralized data storage system. For this, our back end guys also wrote integration tests.

They also integrated Sentry for one-time exception tracking to control our complete code. This works like a fire alarm and alerts us if something isn’t running as its supposed to in our system.

This is how our Sentry integration looks like

Filip, one of our backend developers, created an Ethereum Event Writer. So how does it work? It sees Ethereum events which are getting recorded in our system and as soon as someone uses a smart contract we get a notification in our system. We use a message queues system for our platform. This allows us to have a reliable and an asynchronous way to read from the Ethereum blockchain and communicate between our services. We treat events on the blockchain as the source of truth, but we do not implement reading from it in all of our microservices. Thus we have introduced the Ethereum Event Writer service to republish each Ethereum event into the platform message queue. The biggest challenge in this microservice is to respect possible implementation changes of smart contracts. Our solution is to handle this case with a proxy pattern in our main smart contract — the Universe (= name of our main smart contract).

This is how the architecture of the Ethereum Event Writer looks like

Neufund on Tour

We had a great time during out TOA satellite event. Even the weather was on our side! Our VP ventures Agnieszka Sarnecka did three amazing workshops about fundraising on Blockchain on a boat which we had organized for the event. Each cruise took us up the Spree all the way from Funkhaus, where TOA takes place every year, into Berlin. We welcomed some lovely people including investors, companies, bloggers, and crypto-enthusiasts on board and exchanged news ideas and thoughts. Till next year!