When I came to RC it was with the intention of working on something called conscious computation – how to use computation to make us more conscious (not to affect our consciousness like some psyop or MKUltra project).  There is also the inverse question of what consciousness means for a computer and does a computer have an unconscious, but I wont be working on that right now. Today I made some strides in my road map, my dev environment and stack and I created an org on github : consciouscomputation.

My main project is a prayer blockchain.  My plan is to implement a prayer as a NFT (non-fungible token) – or perhaps extend the NFT and create a new type of ERC token.  Tomorrow I am having a brainstorming session to help hammer out some design and functional issues around the creation of a prayer token – and come up with a name. Some questions are:

• What does it mean to own a prayer? Can we come up with some idea of communal ownership, or non-ownership?
• How is a prayer created?  Do people submit prayers and then one is randomly selected to be instantiated? Do people vote on prayers? Do you buy a prayer (NO!)? Can you create a prayer with another prayer (e.g., create a liturgy)?  Can you create a prayer with an object (e.g., create a ritual)? We could probably do a bunch of these things but I will start with one.
• What kinds of things can prayers do? Can they donate to a charity? Can they call a friend? Do they just print a mantra to the blockchain? It will probably be something simple to start but I would like this to be extensible enough so people can add different activations. How do we make the prayer extensible without having to program in solidity – how can it be as easy as integrating with a REST API – how can we just add I/O (or really just Output)
• What kinds of things can people do with prayers? They can make a prayer. They can amplify a prayer, like I can take someone’s prayer and pray with that prayer. What does that mean for the prayer. It accumulates more value – but what does that value translate into.
• How do you remove a prayer? How do you monitor bad or hurtful prayers – prayers that are not really prayers?
• What kind of blockchain will this run on – the main ethereum blockchain or should I run a parallel blockchain or PoA ethereum chain. (This is not really contract related – but it relates to the next question)
• How are prayers mined? Why is it important that the we know which prayers were actually made and that the blockchain validates this? Why do we need crypto? Why do we need a blockchain? I would say there it is important to have social proof and public proof of the prayers (wishes and desires) of human kind. That a 51% attack would create a  false consciousness  – where by we would be deluded as to the state of what people truly desire (fake news anyone).

As of today I plan on using the Ethereum blockchain, ReactJS,  the truffle contract framework, node for backend, mongo for caching and perhaps data not persisting to the blockchain, and  metamask for login, all to be deployed on AWS (or maybe heroku) – or maybe microservices with lambda. If I decide to run my own blockchain it will probably be an Ethereum PoA blockchain.  I am going to deploy with Terraform.

But I cannot forget the small side projects. I continued working on my Haskell learning project and the work is coalescing around a virtual prayer wheel. I will put these side projects in their own github repo under the conscious computation org. This one is called “prayertech”, and hopefully I can integrate some of the shader work I did a few days ago and make a 3D prayer wheel that generates mantras with Haskell. I learned that  Euterpea does not work with Haskell stack, so I am looking for a new music library or maybe I just wont use stack for this. As I continue to build out the prayer blockchain, I will probably take a hour or so a day and work on a toy project related to conscious computation but exploring a new topic – maybe a new language or library, or technology such as cryptography or machine learning, or to explore an idea.