# Preliminary CredSperiment Cred

**URL:** <https://discourse.sourcecred.io/t/preliminary-credsperiment-cred/219>\
**Category:** The CredSperiment\
**Created:** [September 19, 2019, 1:07pm UTC](https://discourse.sourcecred.io/t/preliminary-credsperiment-cred/219 "2019-09-19T13:07:20Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Beanow](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/beanow/32/98_2.png) [@Beanow](https://discourse.sourcecred.io/u/Beanow)\
**Post date:** [September 20, 2019, 10:00am UTC](https://discourse.sourcecred.io/t/preliminary-credsperiment-cred/219/7 "2019-09-20T10:00:47Z")

</div>

> [@decentralion](#):
>
> I’m planning to write a roadmap document in the coming week which goes in depth on these tradeoffs, and will be happy for reviews and feedback at that time.

Most critical for real money scenarios imo is to find the requirements for and designing a _ledger_. The most urgent quality improvements may be derived from that to an extent.

A place to look for ideas is “event sourcing”. It’s a pattern where your source of truth is not mutable tables (the typical DB design) but an immutable array of events. It’s particularly well suited for situations where you need auditability. And using it should be familiar if you have used for example redux for reducing events to an app state.

---

_[View the full topic](https://discourse.sourcecred.io/t/preliminary-credsperiment-cred/219)._