OLE natural blockchain language prevents errors. Programmers are used to write code & test it afterwards. Does it sound familiar? The problem with testing is that you can find one error or even a few, but you can never be sure you found all all of them. OLE checks your output code upfront, and forces programmers to work structured, assuring quality . Blockchain is great, but garbage in is garbage out is valid more than ever. To program blockchain nowadays. programmers need to work more secure. You see this testing mindset also elsewhere. The Intel / Heart-bleed scandal shows that software is too critical to our society to guess code. You need a proof mechanism. We cannot have the situation that "someone has forgotten something", like in this case, a missing security layer. When you program a blockchain wrong, you get a terrible repetitive error, like Heart-bleed. Blockchain errors are even worse, real contract are lost. Wrong contracts are placed on the blockchain, and once on the bloc...
We founded the BLOCKCHAIN KNOWLEDGE FOUNDATION (or BKS). Before we were colleagues at the University of Groningen. This University was founded 1614, a top global top 100 university.
We are all men from the North, we like our region and we are happy to have large data companies and institutions in our town, like Duo.nl (de facto Ministry of ICT) or Gasunie.nl (The EU gas roundabout, storage and production). Also financial institutions love settling in the North of the Netherlands, known for the integrity.
`"Semi-open software" means that we need 2 years to get the community up and running. Only then, it cannot be hijacked by the big commercial companies. Digital multinationals just re-wrap "open source" and buy away talent. In approximately 2 years we plan to release the source CODE. this is approximately the same time it takes to figure out how OLE is built and used, we guess. We have OLE users among top enterprises & government.We aim to achieve more independence on strategic commercial technology .