- for those who pay attention - core features are well-designed. Well-covered with tests.
  
  ----
- Protocol iself is 100% certified with coverage tests - properties are proven! 
- Full coverage is equivalent to mathematical proof (given that program terminates), no need to use proof assistant.
- Ideally, proofs by coverage should be done on Turing-machine (inc, dec, jmp)
- c8 coverage is just "good enough"; at the least, it is better than migrating Isabelle proofs to Haskell (Cardano practice).
  
  ----
- non-essential features are in minimum viable state: no one invested in time to refactor and re-design. It's just 2 months work here.
  
  ----
- service architecture is well-designed. It is NOT monolitic, NOT tangled in dependencies. Docs have diagrams - if you look for it.
- I did not split components into several repos - because party declined investing into it.
- It gets complex around cryptography because it should.

  ----
- No frameworks: frameworks (for unit tests, UI, React etc) would not give any actual advantage: IoC is just a pattern. This is my position here, not party's - party did not care.

  ----
- For the complexity of this product - the result is better than what team tasked with same problem would output in a year. I engineered for over a decade, can attest.
- Don't forget: this is novel solution supporting something often thought impossible: secure BTC contracts of any complexity, purely trust-less oracless.
- It is a result of long-term research in Bitcoin. It is more research than Cardano did ever. And with results, unlike Cardano.

  ----
- I kept many files in root - I know that.
- I did not clean up - because was not paid to do so. I warned the party aboput consequences repeatedly.
- Invest proper funds - you'll get clean code and repo. If you haha with me - I'll keep the state of repo like this, u get haha results.

  ----
- I ignored commit messages and many practices - to prevent party from integrating with this product. 
- I am the only one who remebers what supposed to be where and what means what. And I warned party - this will happen.
- That's because party ignored Wolfram Alpha targeting and wanted boxing matches stats to be here. The odds are rigged and PoW-certification is useless for that, since services are centralized. Boxing is gay. Play football!

  ----
- legal note: party comitted serious fiancial crime (NOT related to this project) - as I dicovered. They took around million usd for meaningless one-day feature, they did not even implement it - Cardano Marlowe implemented for them (as commits prove). They extracted a million using Cardano's public funding. Not surprising to me, given Charles irradic behavior and community-ideas. I reported to Cardano and Wolfram as soon as dicovered, and warned them about this party way before, since I used to work in IOHK.
- I read a lecture about spending habbits to the party.
- I read a lecture about treasury management to Charles Hoskinson
- I read a lecture about outbranding and outsourcing to Stephen Wolfram
  
  ----
- "Dirty code making dev dirty" - is a superstition :). Dirty code developes immune system.

  ----
### Bottom line

Status of the product: hibernated

This product is commercial - so:
- extra funds have to be invested into proper maintainability
- I can refactor myself - should go without saying
- main concern: proper target systems have to be found for it.
