GM everyone,
beloved and most respected community,
I’d like to briefly share the current status of the project, some hurdles I’m encountering, the plans to resolve them, and what’s coming next.
Phase 3 should have been finished by now, but we’ve slipped slightly from the projected timeline due to some unforeseen challenges.
Rest assured, we will push this through.
I would love to give you a new timeline and deadlines, but I’m afraid of disappointing you again if I don’t deliver exactly on time. I hope you can understand the situation: I’m working on the project daily, actively debugging issues, and constantly thinking about how to fix them.
The issues are resolvable. I don’t have an ETA yet, but I do have a clear plan to resolve them effectively. It will, however, require a slight delay.
Current state of the project :
1. Alpha engines (I, II, III and alpha-T)
These have been implemented and the codebase is solid. What remains is hardening: security tests, failure tests, edge-case tests, and KATs.
Writing the tests is straightforward; running full end-to-end testing takes time (estimated 2–3 days).
2. Network architecture (node propagation, headers, topology, etc.)
This is not yet implemented. The previous testnet ran from a central server and a central orchestrator to simplify things, which is why it was smooth.
To go to full workable testnet, we need to build a proper network architecture so that nodes can connect to each other (e.g., via P2P, gossip protocols, etc.).
Estimated: 4–6 days for implementation, plus 2–3 days for testing.
3. Server and database
Right now, Obex runs in 2 modes: local database and cloud database.
To make this with good quality grade, I need to design the database architecture properly how to store accounts (addresses), their details, and keys in a secure environment.
For now it’s managed by a cloud server, it’s secure, but basic.
Estimated: about 3–4 days for implementation, plus 1 day for testing.
Once we complete this round of development, fixes, and testing, we will move to Phase 3: polishing the UI and getting Obex ready for investor pitches.
Serious development is quality development, and quality development requires serious time and effort. I really hope you can give me the space and time to execute this properly.
Your support means everything to me, and I will give my best every bit of effort I have to deliver.
Thank you for your patience.
Thank you for supporting the project.
Thank you for being part of this community.
Much love,
aminnizamdev ✊🏻
beloved and most respected community,
I’d like to briefly share the current status of the project, some hurdles I’m encountering, the plans to resolve them, and what’s coming next.
Phase 3 should have been finished by now, but we’ve slipped slightly from the projected timeline due to some unforeseen challenges.
Rest assured, we will push this through.
I would love to give you a new timeline and deadlines, but I’m afraid of disappointing you again if I don’t deliver exactly on time. I hope you can understand the situation: I’m working on the project daily, actively debugging issues, and constantly thinking about how to fix them.
The issues are resolvable. I don’t have an ETA yet, but I do have a clear plan to resolve them effectively. It will, however, require a slight delay.
Current state of the project :
1. Alpha engines (I, II, III and alpha-T)
These have been implemented and the codebase is solid. What remains is hardening: security tests, failure tests, edge-case tests, and KATs.
Writing the tests is straightforward; running full end-to-end testing takes time (estimated 2–3 days).
2. Network architecture (node propagation, headers, topology, etc.)
This is not yet implemented. The previous testnet ran from a central server and a central orchestrator to simplify things, which is why it was smooth.
To go to full workable testnet, we need to build a proper network architecture so that nodes can connect to each other (e.g., via P2P, gossip protocols, etc.).
Estimated: 4–6 days for implementation, plus 2–3 days for testing.
3. Server and database
Right now, Obex runs in 2 modes: local database and cloud database.
To make this with good quality grade, I need to design the database architecture properly how to store accounts (addresses), their details, and keys in a secure environment.
For now it’s managed by a cloud server, it’s secure, but basic.
Estimated: about 3–4 days for implementation, plus 1 day for testing.
Once we complete this round of development, fixes, and testing, we will move to Phase 3: polishing the UI and getting Obex ready for investor pitches.
Serious development is quality development, and quality development requires serious time and effort. I really hope you can give me the space and time to execute this properly.
Your support means everything to me, and I will give my best every bit of effort I have to deliver.
Thank you for your patience.
Thank you for supporting the project.
Thank you for being part of this community.
Much love,
aminnizamdev ✊🏻
❤13
OBEX PORTAL pinned «GM everyone, beloved and most respected community, I’d like to briefly share the current status of the project, some hurdles I’m encountering, the plans to resolve them, and what’s coming next. Phase 3 should have been finished by now, but we’ve slipped…»
however good the technology or the codes is , it’s just numbers and alphabets in the github repository, it’s the people , the support and the convictions of the community that push and make a project excel .
it’s them who actually make it valuable .
with my humblest heart, i apologize for the delayed and the bad communication etiques for the past few weeks .
striving to do better
it’s them who actually make it valuable .
with my humblest heart, i apologize for the delayed and the bad communication etiques for the past few weeks .
striving to do better
❤26👎3👍1
OBEX IS BACK.
Eight months ago, I started rebuilding.
Today, OBEX launches a new chapter on Robinhood Chain.
OBEX is deterministic infrastructure for onchain finance. In simple terms, it moves critical decisions out of the hands of whoever happens to control the next block and puts them into explicit protocol rules.
Participation is determined through RAM-hard Proof-of-Effort and verifiable randomness. Blocks are validated through deterministic rules. Transactions follow canonical ordering, removing discretionary reordering as a source of MEV. Rewards are calculated independently of who proposes the block.
Same inputs. Same rules. Same result.
But why did OBEX disappear?
The original project launched on Solana. It reached a $1.7M ATH, but I didn’t have the resources to keep funding the infrastructure, development and operating costs required to take it further.
So the project was abandoned.
The idea wasn’t.
Over the last eight months, OBEX has been rebuilt from the ground up and brought to production readiness.
I chose Robinhood Chain as the new home because its focus on programmable financial infrastructure and tokenized assets makes it a natural environment for what OBEX is designed to become.
Today, I am launching a new native $OBEX token on Robinhood Chain.
This is not a migration of the old token. It is a completely fresh deployment and a new beginning for the protocol.
The first OBEX proved the idea could attract attention.
This one is built to actually go somewhere.
One final note for the community:
Unfortunately, I was locked out of the original OBEX X account and no longer have access to the email connected to it, as it has been quite some time since the original project was active.
To verify that this is the same person behind the original OBEX, I’ll be using the original OG Telegram group/channel as proof of continuity.
The old account may be gone.
I’m not. OBEX isn’t.
OBEX is live.
CA: 0x2db219a4c16f1bae611361d21421fde06f447f47
Eight months ago, I started rebuilding.
Today, OBEX launches a new chapter on Robinhood Chain.
OBEX is deterministic infrastructure for onchain finance. In simple terms, it moves critical decisions out of the hands of whoever happens to control the next block and puts them into explicit protocol rules.
Participation is determined through RAM-hard Proof-of-Effort and verifiable randomness. Blocks are validated through deterministic rules. Transactions follow canonical ordering, removing discretionary reordering as a source of MEV. Rewards are calculated independently of who proposes the block.
Same inputs. Same rules. Same result.
But why did OBEX disappear?
The original project launched on Solana. It reached a $1.7M ATH, but I didn’t have the resources to keep funding the infrastructure, development and operating costs required to take it further.
So the project was abandoned.
The idea wasn’t.
Over the last eight months, OBEX has been rebuilt from the ground up and brought to production readiness.
I chose Robinhood Chain as the new home because its focus on programmable financial infrastructure and tokenized assets makes it a natural environment for what OBEX is designed to become.
Today, I am launching a new native $OBEX token on Robinhood Chain.
This is not a migration of the old token. It is a completely fresh deployment and a new beginning for the protocol.
The first OBEX proved the idea could attract attention.
This one is built to actually go somewhere.
One final note for the community:
Unfortunately, I was locked out of the original OBEX X account and no longer have access to the email connected to it, as it has been quite some time since the original project was active.
To verify that this is the same person behind the original OBEX, I’ll be using the original OG Telegram group/channel as proof of continuity.
The old account may be gone.
I’m not. OBEX isn’t.
OBEX is live.
CA: 0x2db219a4c16f1bae611361d21421fde06f447f47
🤣13❤7👎6🔥1