Background
Betakronan was started to respond to the Riksbank's wish to receive
comments on the e-krona project. A project aimed at investigating and
developing a state-guaranteed digital supplement to cash.
For us it is obvious that everyone should be able to participate in the
digital economy. We consider it a fundamental right to be able to take
part in the social infrastructure that payment services make up. We do
not think that the participation of individuals should be conditional
on a customer relationship with a private bank.
Unfortunately, vulnerable groups such as paperless, new arrivals and
people outside the banking system are often restricted to physical
cash. This creates difficulties for them to participate in society.
Even wealthy groups such as tourists and business travelers experience
thresholds to participate fully in the economy in Sweden. For us it is
self-evident that all groups should be included in a solution for
the e-krona.
Platform
The implementation is based on the Hyperledger Fabric block chain platform with the Hyperledger Composer tool. The source code is available on Github.
You can also take a closer look at Betakronan's API. Click below to see more how it works.
api.betakronan.se
Test it!
Do you want to experiment yourself with Betakronan? In order to access our block chain, an ID card is required. Mail us at einar.persson@iteam.se and we will get back to you!
We have built a simple simulation of an online payment page that uses e-krona for payment via QR code. So far without identification method.
try.snowflake.cash
Read our response
The Riksbank asked Sweden's technology companies and developers to tell about their vision for the e-krona. We want the Riksbank to:
- Explore multiple tracks in parallel - where block chain technology is one track
- Allow a longer development period where understanding and architecture grow
- Enlist different skills (economists, designers, behavioral scientists, hackers, ...)
- Be radically open and transparent in the process
- Avoid "The Big Procurement" with an enormous requirement specification that inevitably becomes hopelessly out of date within 3 years