Skip to content

Open points

reviewed: 8 January 2026

Current pool of tasks

  1. ✅ Pheix project «FTB — The Patch» Release
    • Add announcement to blog, both for pheix.org and narkhov.pro;
    • Update Release top panel text;
    • Raise Merge Request !33:
      • Add description based on !32;
      • Add link to the Postmortem report;
      • Test it on Ethereum public network Hoodi.
    • Fix the explicit version verification skip for master branch: #234;
    • Allow query strings in blog pages: #235.
  2. Authenticate user via MetaMask in Pheix project: feature post-merge:
  3. ERC20-token funding/charging for PM25/Ethelia project, details: @pheix-io/ethelia#37;
  4. Upgrade Ethereum Local Network:
    • Cancun infrastructure: separate validator(s) and 2x Geth execution clients with built-in beacon clients;
    • Run clef instance for one node (1st or 2nd, no matter);
    • Upgrade/refactor tests for smart-contacts project according the new network upgrades: @smart-contracts#33;
    • Introduce clef authentication module in Pheix project: #174;
    • Remove personal namespace from start up script: @pheix-research/ethereum-local-network#9
  5. Infrastructure monitoring and log collecting system via Prometheus→PushGateway→AlertManager: @raku-dossier-prototype#9:
  6. PM25/Ethelia project and Dossier telegram bot:
    • Extract PM2.5 sensor values from photos (OCR): @raku-dossier-prototype#6;
    • Smart telegram bot monitoring and possible restart: @pheix-research/raku-dossier-prototype#9;
    • Embed micro web-server with /metrics route to deliver generic bot metrics to Prometheus;
    • Asynchronous dumper for keystores, dossiers, logs, configs and other important data stored inside the container: safe remove/prune/delete feature:
      • Add async dump feature to Telegram bot — create tgz dump file on bot start, save tgz dump file to shared folder;
      • Add crontab job to copy tgz dump file from share folder to archive location;
    • Add /faucet 0xdf...3c feature to bot: a simple way to get some AlaAuETH to get started with authentication feature.
  7. PM25/Ethelia project launch: @pheix-io/ethelia#40;
    • trx-advancer: review latest implementation and add  ???  functionality to get transactions from a mempool, in general we have to introduce the tools for quick identification and fixing the next situation:
      • current nonce is X;
      • we commit signed transaction with nince X+100: transaction stuck and will never be mined;
      • trx-advancer should be able to find that transaction and somehow restore the nonce sequence: get stuck transaction's input and create a new transaction with X+1 nonce;
    • Update Ethereum authenticator and Telegram bot containers to use shared folders for external data: we have to be able to delete and create containers without data loss.
  8. Official Ethelia Landing Page improvements:
    • Add authentication form and all related features;
    • Update content (slide with details):
      • Cube and Sphere smart sensors;
      • pm25.online service;
      • API documentation link to main navigation block;
      • Getting started page: add link to main navigation block and translate to English.
  9. Perform primary to secondary server switch on outages or issues:
    • Backend async checker script: it will collect metrics from given backends every 2 minutes and set the most suitable for use on tailless instance (via basic and session endpoint as config.json).
  10. Update Cube sensor new prototype:
    • new STL model (CubeV2) with:
      • ready to plug-in PM2.5 sensor: @pheix-io/ethelia#43;
      • no holes;
      • non-removable front panel (reference: the plastic prototype with putty);
      • sharp edges: cantellation.
    • Print CubeV2 in plastic;
    • CubeV2 in aluminum.

 Work in progress: new items to be defined and announced. 

Pinky paper

  1. Ethelia technical concept: Telegram, Geth, Pheix and Ethelia as an add-on module;
  2. Technical part from marketing perspective: finally we have to do full rewrite of tech part in human/investor readable way, collect details from:
  3. Monetization and product payback:
    • PM2.5 project funding model: #37;
    • since fixed limit for event search is introduced, different paid subscriptions could increase/decrease this setting;
    • event subscription — «events-on-air» feature on remote endpoint or in administrative panel, also consider filters and proxy/relay to external services like Telegram, Matrix, Slack, Discord or traditional email as a future improvements;
    • plan «pay per device» — we will define the limit for free-of-charge event sources, any additional source should be paid;
    • plans «pay per request» or «pay per auth» — request cost is 20x lower for example, but auth is much more flexible for enterprise clients;
    • generally Ethelia is a gateway to public, private (scale the higher number of nodes), virtual (cloud hosted) and local (single CPU) networks — there could be any pricing plans, like «pay per node» — increase number of nodes and make it much more decentralized, «pay per CPU» — scale your local network, «pay per resource» — manage your cloud;
    • plan «pay per transaction» — /pheix-io/unilode/-/issues/1#subscription-details;
    • since the registration model via Telegram bot is used, we can introduce different paid plans in TON coins, the most reasonable one «pay per function» — customer pays for advanced bot functions (mostly taken from administrative panel);
    • admin panel integration to 3rd-party websites requires cross domain cookies to be allowed, so SameSite should be set to None instead of Strict — it's configurable and customer might be charged to allow that feature;
    • investment models for PM25/Ethelia project based on ERC20 token listings and long-term historical data usage/sharing perspectives: PDF;
  4. Future improvements, prospects and road map (3 years vision).

Extended technical details

Pheix database on blockchain optimization/improvement

It was moved to Deprecated section: /rawhide/deprecated/op/event-driven-database.

This optimization/improvement has no sense in general cause of use of EIP-4844 blob transactions. The PheixDatabase smart contract was improved at @pheix-research/smart-contracts#48.

Authorization on event source

Now we have to pass auth on Ethereum node and get the access token. This token might be changed in some time interval, so:

  • deliver new token somehow to event source;
  • just add authorization step to event source software/firmware.

Both solutions are very expensive and we need something lightweight and reliable. I suggest to consider subscription feature available in Geth.

Static tokens were introduced at 2a720ea3 and this is the possible compromise for now.