Socials updated,
Community informed,
I will lock in now, building our dream .
Till then, much love #Obexian 🔥
Community informed,
I will lock in now, building our dream .
Till then, much love #Obexian 🔥
❤11💯1👾1
This media is not supported in your browser
VIEW IN TELEGRAM
Update : Obex Protocol
We are pleased to share the following important updates:
• Legal status: Obex Protocol is now a legally registered business and organization focused on a distributed operating system (blockchain).
• X verification: We submitted an application for X verification (gold checkmark) yesterday. The request is currently under review; if approved, the verification may be granted this week.
• Development & whitepaper: The codebase is under active development and undergoing edge-case testing. An initial draft of the whitepaper has been started.
• Website work (today): While testing continues, I will be reworking the official website: https://obexprotocol.io.
Further updates will be provided as progress is made. Thank you for your continued support.
We are pleased to share the following important updates:
• Legal status: Obex Protocol is now a legally registered business and organization focused on a distributed operating system (blockchain).
• X verification: We submitted an application for X verification (gold checkmark) yesterday. The request is currently under review; if approved, the verification may be granted this week.
• Development & whitepaper: The codebase is under active development and undergoing edge-case testing. An initial draft of the whitepaper has been started.
• Website work (today): While testing continues, I will be reworking the official website: https://obexprotocol.io.
Further updates will be provided as progress is made. Thank you for your continued support.
❤12🔥2
Dear Obexian,
Testnet Phase 3 will be launched this Sunday.
Stay tune . Buckle up
Testnet Phase 3 will be launched this Sunday.
Stay tune . Buckle up
❤14👏2🔥1
OBEXIANS!
Testnet phase 3 will now commence Monday from the result of a community vote.
See you then
Testnet phase 3 will now commence Monday from the result of a community vote.
See you then
👍12❤3🤨2🙏1
Guys, its so close but issues still persist. in a group with few devs trying to solve it .
❤10👍2🔥2
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
❤21👍1