Deprecated: Return type of Pimple\Container::offsetExists($id) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data01/virt126885/domeenid/www.saksadogi.com/codegurus.eu/wp-content/plugins/ithemes-security-pro/vendor-prod/pimple/pimple/src/Pimple/Container.php on line 133

Deprecated: Return type of Pimple\Container::offsetGet($id) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data01/virt126885/domeenid/www.saksadogi.com/codegurus.eu/wp-content/plugins/ithemes-security-pro/vendor-prod/pimple/pimple/src/Pimple/Container.php on line 98

Deprecated: Return type of Pimple\Container::offsetSet($id, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data01/virt126885/domeenid/www.saksadogi.com/codegurus.eu/wp-content/plugins/ithemes-security-pro/vendor-prod/pimple/pimple/src/Pimple/Container.php on line 79

Deprecated: Return type of Pimple\Container::offsetUnset($id) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data01/virt126885/domeenid/www.saksadogi.com/codegurus.eu/wp-content/plugins/ithemes-security-pro/vendor-prod/pimple/pimple/src/Pimple/Container.php on line 143

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data01/virt126885/domeenid/www.saksadogi.com/codegurus.eu/wp-content/plugins/ithemes-security-pro/core/lib/lockout/execute-lock/abstract-context.php on line 60

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data01/virt126885/domeenid/www.saksadogi.com/codegurus.eu/wp-content/plugins/ithemes-security-pro/core/lib/lockout/execute-lock/abstract-context.php on line 66

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data01/virt126885/domeenid/www.saksadogi.com/codegurus.eu/wp-content/plugins/ithemes-security-pro/core/lib/lockout/execute-lock/abstract-context.php on line 72

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data01/virt126885/domeenid/www.saksadogi.com/codegurus.eu/wp-content/plugins/ithemes-security-pro/core/lib/lockout/execute-lock/abstract-context.php on line 76

Deprecated: Return type of iThemesSecurity\Lib\Lockout\Execute_Lock\Context::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data01/virt126885/domeenid/www.saksadogi.com/codegurus.eu/wp-content/plugins/ithemes-security-pro/core/lib/lockout/execute-lock/abstract-context.php on line 56

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data01/virt126885/domeenid/www.saksadogi.com/codegurus.eu/wp-content/plugins/ithemes-security-pro/core/lib/class-itsec-lib-distributed-storage.php on line 578

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data01/virt126885/domeenid/www.saksadogi.com/codegurus.eu/wp-content/plugins/ithemes-security-pro/core/lib/class-itsec-lib-distributed-storage.php on line 585

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data01/virt126885/domeenid/www.saksadogi.com/codegurus.eu/wp-content/plugins/ithemes-security-pro/core/lib/class-itsec-lib-distributed-storage.php on line 606

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data01/virt126885/domeenid/www.saksadogi.com/codegurus.eu/wp-content/plugins/ithemes-security-pro/core/lib/class-itsec-lib-distributed-storage.php on line 613

Deprecated: Return type of ITSEC_Lib_Distributed_Storage_Cursor::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /data01/virt126885/domeenid/www.saksadogi.com/codegurus.eu/wp-content/plugins/ithemes-security-pro/core/lib/class-itsec-lib-distributed-storage.php on line 620
Ask HN: Viability of general purpose virus on smart contracts? - CodeGurus

Ask HN: Viability of general purpose virus on smart contracts?

I was checking the hash rate for various coins today, just to get a sense of how much computation gets used, and it was back floating at ~550 EH/s. [1] Eta, 10^18, so, ~5.5*10^20 hashes a second.

I was walking around, and thought “If I was malicious, I might want the Earth to calculate 10^20 virus calculations for me a second”

From lightly checking, it seems like there’s already a malicious smart contract market, and anti-market. [2] However, most seem to be directly targeted at the blockchain and stealing your coins, rather than general purpose virus propagation.

However, I don’t really know enough about the technicalities of smart contract processing.

Question: Is it possible to write a general purpose virus that will propagate with every hash calculation or coin transaction (any major coin, although Bitcoin’s the obvious 1st choice with 10^20 hashes a second and $1T market cap).

Possible stuff that’s not steal your wallet: bootloader, configurator, shredder, botnet link, lightweight VM, keylogger, adware, automated downloader, activity monitor, duplicator, bricker, tracert, or an exit node logger.

Is any of that stuff viable on a smart contract execution? Is this something people should have any concern about?

[1] BTC Hash rate: https://www.blockchain.com/explorer/charts/hash-rate

[2] Smart Contract Exploits, https://pixelplex.io/blog/smart-contract-vulnerabilities/

Comments URL: https://news.ycombinator.com/item?id=39685631

Points: 1

# Comments: 0


Posted

in

by

Tags:

Comments

Leave a Reply