TLDR
Yes, probably, but it will be very difficult to build.
Just like buses, none for ages and then two in short succession
Yesterday, I got very excited about this subject (it doesn’t take much) because I had an epiphany about the transactions costs being covered by the annual/monthly software costs that it would replace…
Today I have given the project I was about to throw myself into some more thought before committing some real money to it.
These are my thoughts.
Fortunately I’ve given this some more thought before signing up for a dedicated server at an annual cost of around Β£1,300 for what will be a valiant side quest to my normal day to day endeavours.
Not impossible, just very very difficult.
Structure
For example, just to establish multiuser access to one set of accounts where users have varying levels of read/write permissions and different accounts to manage …
Using roles, rules and badges?
Feasible, but just as complex as i remember because of all the possible permutations.
For the transactions, I had one main master table that functioned as the general ledger/cashbook/bank account in my original design and tables for account type (income, expense, taxation, capital, asset/liability etc.,), accounts, stakeholders, third parties and entity details, for example.
It’s hard to see what and how i would use fungible/non-fungible resources to establish the necessary relationships i had in my original database using views and stored procedures on unique indexes.
Do i use different tokens having different account types or can i define types using nfts?
Do i mint and burn tokens to represent debits or credits or just swap balances as is traditional.
Or a combination?
Reality bites.
My initial excitement has been tempered.
I still think radix could be up for the job but for now I will put this project back on the slow burner where it’s been for a very long time..
Just as well no one reads these posts hey.π
I’m trying to manage my lofty expectations. π
xrd πͺπ₯π₯