Obyte: Totally new consensus algorithm + private untraceable payments

[tonych]

Autonomous Agents are finally coming to mainnet

https://medium.com/obyte/autonomous-agents-on-mainnet-ready-for-takeoff-d89b50e6d921?source=friends_link&sk=c140a08d2c69eef8b87785f567dd4723



Autonomous Agents are set to activate at MCI 5,210,000 which is expected at the end of February. Since this is a protocol upgrade and therefore a breaking change, all nodes, including light nodes, need to upgrade to version 3.0.0 that was released today.

For full nodes (both headless and GUI), the upgrade will take a very long time since the update also includes moving part of the data from SQLite database to a much faster RocksDB database. The move will improve performance of some queries, especially data feed queries that some AAs might actively use. The conversion of data will be done when you launch the wallet for the first time after the upgrade and it will take several hours (in our experience, from 3 hours on a dedicated server to 39 hours on a VPS), so please plan you update accordingly. RocksDB database will take additional 15 GB of disk space (but the data that remains in SQLite will grow a bit slower after the upgrade), please check that you have enough free disk space before the upgrade.

For light nodes, the upgrade will be much faster since their database is usually small, but light nodes with long transaction history can still experience a noticeable delay during the first start, especially mobile ones on older hardware.

Create a backup before upgrading.

Bittrex and other exchanges have already been notified about the need to update. They will have to pause deposits/withdrawals for many hours during the updates of their wallets, please plan accordingly.

[1679430664]

1679430664

[1679430664]

1679430664

[1679430664]

1679430664

[Choosewise]

Are there any other coins with AA implementation?

[tarmo888]

Are there any other coins with AA implementation?

Yes, it is same what other mistakenly call "smart-contracts". Obyte already calls smart-contracts those addresses, which have basic spending restrictions (lot more options than Bitcoin has with OP codes). https://developer.obyte.org/contracts/reference

Even Ethereum called their smart-contracts as Autonomous Agents in the white paper https://github.com/ethereum/wiki/wiki/White-Paper#ethereum-accounts and there have been debates on changing the name to something else https://twitter.com/vitalikbuterin/status/1051160932699770882

Biggest difference is that Oscript language is more like declarative and is basically dynamic address definition with placeholders while Solidity is imperative language. Also, Oscript gives you less rope to hang yourself, so you can't use loops, but otherwise Obyte Autonomous Agents give developers access to more features than Ethereum comes with out of the box. https://developer.obyte.org/autonomous-agents/oscript-language-reference

[PochJvb]

This coin almost collapsed in Jan 2018 it was over 900$ and now 27$. If you think this coin has the potential then it's the right time to buy this coin.

[tarmo888]

This coin almost collapsed in Jan 2018 it was over 900$ and now 27$. If you think this coin has the potential then it's the right time to buy this coin.

Yeah, and people need to make some noise about upcoming Autonomous Agents, it is not going to market itself. It can have the best technology, but that's useless if everybody just sits on their bag.

[tonych]

An important security update is released.  It fixes two serious vulnerabilities discovered and reported to us by security researcher pearl:

*    text messages in chat were incorrectly handled which allowed attackers to execute arbitrary code on victim's wallet. An attacker could supply arbitrary code in angularjs {{}} expressions and the victim's wallet would evaluate it. The attack vector could be used to steal the private keys. The vulnerability existed in all versions of Obyte wallet since the first release in 2016. However, to exploit the vulnerability, an attacker needs to first trick the victim to pair with the attacker's wallet or chatbot. Users who had their wallets protected with a good password and seed words deleted were better protected against such an attack. We have no reports of this vulnerability being actually exploited. The fix makes sure that user input is always treated as text and never evaluated.

*    restore from full backup function allowed file paths with directory traversal (../) characters in backup archive, which could enable an attacker to overwrite important user files, such as .bashrc. on Linux. The vulnerability existed in all versions of Obyte wallet since restore from full backup was introduced in mid 2017. However, to exploit the vulnerability, an attacker needs to first trick the victim to restore from a maliciously crafted backup file. We have no reports of this vulnerability being actually exploited. The fix checks for directory traversal characters in file paths in the backup archive and ignores such files.

Since the two vulnerabilities are now publicly disclosed and each can be used to inflict serious damage to Obyte users who are not aware of them yet, the hub at obyte.org will refuse connections from non-upgraded wallets to keep them safe. All known operators of other hubs have been notified and recommended to apply the same policy.

Only GUI wallets are affected by the vulnerabilities and the upgrade is mandatory for them, headless nodes (wallets, hubs, relays) are not affected.

Please upgrade https://github.com/byteball/obyte-gui-wallet/releases

[buksan]

An important security update is released.  It fixes two serious vulnerabilities discovered and reported to us by security researcher pearl:

*    text messages in chat were incorrectly handled which allowed attackers to execute arbitrary code on victim's wallet. An attacker could supply arbitrary code in angularjs {{}} expressions and the victim's wallet would evaluate it. The attack vector could be used to steal the private keys. The vulnerability existed in all versions of Obyte wallet since the first release in 2016. However, to exploit the vulnerability, an attacker needs to first trick the victim to pair with the attacker's wallet or chatbot. Users who had their wallets protected with a good password and seed words deleted were better protected against such an attack. We have no reports of this vulnerability being actually exploited. The fix makes sure that user input is always treated as text and never evaluated.

*    restore from full backup function allowed file paths with directory traversal (../) characters in backup archive, which could enable an attacker to overwrite important user files, such as .bashrc. on Linux. The vulnerability existed in all versions of Obyte wallet since restore from full backup was introduced in mid 2017. However, to exploit the vulnerability, an attacker needs to first trick the victim to restore from a maliciously crafted backup file. We have no reports of this vulnerability being actually exploited. The fix checks for directory traversal characters in file paths in the backup archive and ignores such files.

Since the two vulnerabilities are now publicly disclosed and each can be used to inflict serious damage to Obyte users who are not aware of them yet, the hub at obyte.org will refuse connections from non-upgraded wallets to keep them safe. All known operators of other hubs have been notified and recommended to apply the same policy.

Only GUI wallets are affected by the vulnerabilities and the upgrade is mandatory for them, headless nodes (wallets, hubs, relays) are not affected.

Please upgrade https://github.com/byteball/obyte-gui-wallet/releases

After updating, when I try to add a new chat bat, I see this error:
An exception occurred: TypeError: Cannot read property 'replace' of undefined; cause: undefined

I tried to create a new wallet and I can not add any chat bot for the same error.

PS Win64/32

[tarmo888]

After updating, when I try to add a new chat bat, I see this error:
An exception occurred: TypeError: Cannot read property 'replace' of undefined; cause: undefined

I tried to create a new wallet and I can not add any chat bot for the same error.

PS Win64/32

while that gets fixed, you can add bots through that page https://obyte.io/bots

[buksan]

After updating, when I try to add a new chat bat, I see this error:
An exception occurred: TypeError: Cannot read property 'replace' of undefined; cause: undefined

I tried to create a new wallet and I can not add any chat bot for the same error.

PS Win64/32

while that gets fixed, you can add bots through that page https://obyte.io/bots

Thanks. The message signature does not work yet.
Writes an error: wrong signature.

[tonych]

Thanks. The message signature does not work yet.
Writes an error: wrong signature.

Which bot is that?

[buksan]

Thanks. The message signature does not work yet.
Writes an error: wrong signature.

Which bot is that?

At first I couldn't sign my address in Draw Airdrop with message: unknown fields. But then I found out that signing your address is impossible in any bot now.

[tonych]

Thanks. The message signature does not work yet.
Writes an error: wrong signature.

Which bot is that?

At first I couldn't sign my address in Draw Airdrop with message: unknown fields. But then I found out that signing your address is impossible in any bot now.

Draw bot has not been upgraded yet but the draw is suspended anyway.  What other bots did you try?

[buksan]

Thanks. The message signature does not work yet.
Writes an error: wrong signature.

Which bot is that?

At first I couldn't sign my address in Draw Airdrop with message: unknown fields. But then I found out that signing your address is impossible in any bot now.

Draw bot has not been upgraded yet but the draw is suspended anyway.  What other bots did you try?

Signing an address isn't possible in real name attestation bot.
wrong signature

[tonych]

Thanks. The message signature does not work yet.
Writes an error: wrong signature.

Which bot is that?

At first I couldn't sign my address in Draw Airdrop with message: unknown fields. But then I found out that signing your address is impossible in any bot now.

Draw bot has not been upgraded yet but the draw is suspended anyway.  What other bots did you try?

Signing an address isn't possible in real name attestation bot.
wrong signature

Works for me. The bot was updated last night though, signing didn't work yesterday when it was on the old version.

[USBitcoinServices.Com]

I haven't been active on this thread and still have version 2.7.2 Do I have to get a newer version?

[tarmo888]

I haven't been active on this thread and still have version 2.7.2 Do I have to get a newer version?

Yes, the old versions doesn't work anymore because there were vulnerabilities discovered in them. Also, the network will activate Autonomous Agents any time now, which requires the latest wallet version.

[tonych]

Another security update v3.0.2 that fixes several serious vulnerabilities (again discovered and reported to us by security researcher pearl).

The update is mandatory for all nodes.

Other bugfixes and improvements in this release:

* Fixed a bug that crashed the wallet when trying to view bots or smart contract definition
* Fixed a bug that crashed wallets on Windows if username contains non-latin characters
* Restored the display of dollar amounts when sending funds, it was lost in the previous release due to merge error
* Mac app is now notarized by Apple which allows it to be installed on macOS Catalina
* Other minor bugfixes

https://github.com/byteball/obyte-gui-wallet/releases

[DaveF]

I installed the 3.0.2 and it goes to updating the database, please wait. It will take several hours please be patient. then when the OK pops and you click it the app closes.

Windows10 64 bit if that matters.


-Dave

[aigeezer]

I installed the 3.0.2 and it goes to updating the database, please wait. It will take several hours please be patient. then when the OK pops and you click it the app closes.

Windows10 64 bit if that matters.


-Dave

I had the same issue, but it eventually synced after multiple restarts. Also Win10 64.

[DaveF]

I installed the 3.0.2 and it goes to updating the database, please wait. It will take several hours please be patient. then when the OK pops and you click it the app closes.

Windows10 64 bit if that matters.


-Dave

I had the same issue, but it eventually synced after multiple restarts. Also Win10 64.

Client restarts or OS restarts or both? I am working on 5 or 6 times now of the client restart.

-Dave