contratosinteligentes

A smart contract is neither a contract nor smart. It’s a marketing phrase awkwardly slapped onto it.

Let’s imagine something simple: if A deposits 20 $ETH before Friday, the code releases those funds to B. Nobody signs paperwork or calls a notary. The code checks the condition and acts on its own.

What if the condition isn’t met? The code doesn’t need anyone to decide: it simply doesn’t release the funds.

Under the hood, the code lives as copies on thousands of computers that agree on each block of data, linked together with a cryptographic signature that’s almost impossible to break. Each node runs the same copy, so the result is the same for everyone.

This is what they call a smart contract.

But here’s what almost nobody tells you: the code does what it says, not what the team meant. If there’s a bug, it still executes. And since it’s already been published on the network, nobody can go in and fix a line. Fixing it means publishing a new contract or migrating the entire network, and that’s neither quick nor free.

KEY CONCEPTS
- It isn’t a legal contract signed in front of lawyers. It’s code that runs on its own, without traditional legal recourse.
- It doesn’t need a person to check every step. By design, it executes without constant human supervision.
- A programming error doesn’t stop the code from running. It executes anyway, because it can’t distinguish intention from outcome.
- Many contracts rely on oracles to read external data. If the oracle fails, the contract fails—even if its code is perfect.

When people talk about a DeFi hack, this is almost always the cause: a line of code doing exactly what it said, not what someone imagined.

Transparency: Binance may pay us a commission if you trade after clicking an asset symbol or price link in this post.

#ContratosInteligentes #Blockchain #Ethereum #CryptoEducation

NEAR Intents explains the $3.8 million incident: what changed

On October 16, Alex Shevchenko, head of NEAR Intents, published a report on an incident that occurred between September 29 and October 1, 2026.

According to the report, a bug in deposit notifications left balances recorded even after the tokens had been returned. This discrepancy made it possible to withdraw approximately $3.8 million. The team said the issue was in the Intents contract.

CertiK’s October 8 analysis describes USDT payments from the bridge treasury on BNB Smart Chain. Distinguishing between the affected contract, the bridge, and the network helps clarify the scope of the incident.

Shevchenko says the funds were fully recovered on October 2, within 36 hours of detection. He also says affected users were compensated, without specifying that every compensation was made within that timeframe.

The fix was deployed on October 2. Following another critical report, the notification feature was removed on the 7th. The team added checks that compare user balances with the contract’s tokens and trigger an automatic pause if they do not match.

Market update: at 18:03 UTC on October 17, NEAR was trading at 4.923 USDT on Binance, down 1.93% over 24 hours. This price movement does not prove that the report caused it. To assess the risk, it is important to check the fixes and how the routes are functioning; recovering funds in this case does not guarantee they will be recovered in another incident.

$NEAR $USDT $BNB

Educational content. Not financial advice.

#NEAR #DeFi #Seguridad #SmartContracts

🛢 The #petróleo opens higher after mutual attacks by the US and Iran.

#iran #MineralExploration #Inversiones #ContratosInteligentes $BZ $XAU $XAG

#contratosinteligentes
#CNS

#contratosinteligentes #CNS

#Educate the #POPULATION=PROFESSIONAL TRAINING #contratosinteligentes
#CNS