IMDirector

Thanks to the $imd team for recognizing our project at the hackathon. We’re continuing development and getting ready for a live stream.

We hear and carefully study all the recommendations from our users. Much of what has been suggested will be built and implemented.

We continue to move toward our first live stream, featuring interactive engagement with the physical world powered by $IMD tokens. The initial list of devices we’ll connect includes: - an air conditioner (what could possibly go wrong if we let $IMD token holders control the room’s climate? - a speaker - a TV (with channel-switching capabilities) - room lighting, and a drinking water dispenser. We considered adding the ability to turn a computer on or off, but some team members felt that might be a bit too cruel. What do you think? What kind of device-control scenarios would you like to see during the live stream?

Next steps: - Finding a suitable location for the live stream - Interactive scripts - Selecting equipment and developing scenarios for using the equipment with the $imd token - Finding a (blonde with big …) person for the live stream - First live stream

We tested the functionality of the Wi-Fi outlets for receiving $imd tokens and live streams. Outlet 2 - 0.3 $imd - Lamp Outlet 3 - 0.4 $imd - Phone Outlet 4 - 0.6 $imd - Power bank All data and the cost of actions are configured by the live stream director. We can now say that we have all the technical resources needed to carry out our plan. Let’s move on to the next steps of the project.

Done. All 4 Wi-Fi outlets have been added to the service and are working properly. Now let's set the activation cost for each outlet in $imd tokens.

Today, we're scaling up the live streaming system

All done! Now, using a simple Wi-Fi outlet, you can turn on any device by sending it a transaction in the $imd token. We’re building infrastructure for live streaming. It’s important to us that we can quickly switch between outlets and devices. That’s why we created this portable version.

Just build

Could anything bad really happen if we let all $imd token holders turn the streamer’s air conditioner on or off during a live stream? Or unplug his computer from the outlet? I’m sure nothing bad will DEFINITELY happen only good things. I trust you all.

We are building an architecture around the $imd ecosystem for controlling physical devices. But we aren't limiting ourselves to just ESP32 boards; we're testing new devices that will allow us to connect electrical appliances to our live stream more easily and quickly.

We tested Hooks v4 on Relay 4 using our $DIRECTOR token in the Director/IMD pool. Hooks works by buying and selling the token to turn Relay 4 on and off.

We tested our contract deployed on $IMD with our hardware. Currently, we support ESP32-based hardware control with options ranging from 4, 8, 16 relays per board. In our beta version, we tested an ESP32-based board with 4 relays. Payments and actions work as follows: Relay 1 activation - 0.1 $IMD Relay 2 activation - 0.2 $IMD Relay 3 activation - 0.5 $IMD Relay 4 activation – Hooks v4 The $IMD value and the board’s operating conditions for each transaction are set by the stream operator. One of the most important actions takes place on Relay 4. This is where Hooks v4 is located, which allows you to configure the equipment’s operation based on actions in the contract pool.

We submitted an application for the hackathon hosted by $IMD and @imdradar Next up, we'll be testing the hack with an ESP32 board and live streams

$DIRECTOR is live on robinhood chain CA: 0xecb5e7f3b9839eb083dda95099b8438ecebec16e Pair Director/IMD