FLOCK just broke out hard on the 1H chart, with a strong volume spike behind the move. Price is sitting near the recent high, so I’d rather wait for a pullback into the entry zone than chase the candle.
📌 ENTRY: 0.0570 → 0.0590
🎯 TP1: 0.0615 🎯 TP2: 0.0690 🎯 TP3: 0.0820
🛑 SL: 0.0500
⚡ LEVERAGE: 10–25x ⚠️ RISK: Use only 1–2% of your portfolio.
The breakout has momentum, but after a move this fast, the entry matters. If price loses the zone, I’d skip the setup.
FLOCK just broke out hard on the 1H chart, with a strong volume spike behind the move. Price is sitting near the recent high, so I’d rather wait for a pullback into the entry zone than chase the candle.
📌 ENTRY: 0.0570 → 0.0590
🎯 TP1: 0.0615 🎯 TP2: 0.0690 🎯 TP3: 0.0820
🛑 SL: 0.0500
⚡ LEVERAGE: 10–25x ⚠️ RISK: Use only 1–2% of your portfolio.
The breakout has momentum, but after a move this fast, the entry matters. If price loses the zone, I’d skip the setup.
USELESS is holding above the short-term moving averages on the 1H chart after a strong move. Price is currently around $0.2658, with the recent high near $0.2879.
MARSCOIN is holding above the short-term moving averages on the 1H chart after a strong push higher. Price is now consolidating below the recent 0.12181 high.
I’m watching the 0.1100–0.1135 area for a long continuation setup.
HEMI is holding around the $0.0160 area after the strong move earlier. On the 1H chart, price is still sitting around the short-term moving averages, so I’m watching this zone for another push higher.
📌 ENTRY: $0.01600 → $0.01650
🎯 TP1: $0.01800 🎯 TP2: $0.02200 🎯 TP3: $0.02600
🛑 SL: $0.01200
⚡ LEVERAGE: 20x–25x ⚠️ RISK MANAGEMENT: Use only 1% of your portfolio.
If HEMI loses the entry zone and selling volume picks up, I’d stay out instead of forcing the setup.
MARSCOIN is holding above the short-term moving averages on the 1H chart after a strong push higher. Price is now consolidating below the recent 0.12181 high.
I’m watching the 0.1100–0.1135 area for a long continuation setup.
What Reward Splitting Rules a Staking Contract Can Actually Set Spent the afternoon tracing what a staking contract on Dusk is actually allowed to configure and i expected a fairly narrow set of options. it isn't narrow. Dusk's own documentation on Stake Abstraction confirms contracts can implement arbitrary reward splitting rules routing a portion of rewards to referrers affiliates or operators entirely at the contract's own discretion. that's not a fixed protocol level percentage. that's a genuinely open configuration space.$BTR thats the part that stuck. give up protocol enforced simplicity in exchange for letting whoever deploys the contract decide how rewards actually get divided among the people using it. no standard split gets imposed from above.$TAC But hold up i want to be precise about what i actually know here. Dusk names Sozu as the example of this pattern in practice an automated staking pool. What i haven't found documented anywhere is Sozu's current deployment status mainnet live testnet only or something in between. i won't guess at that.@Dusk Kept coming back to what this actually enables regardless of Sozu's specific status referral driven staking services operator fee models affiliate programs all technically possible without needing Dusk itself to build any of them.#dusk So does open reward splitting create genuinely useful staking products or does it just shift the trust question from does Dusk's protocol treat me fairly to does this specific contract's operator treat me fairly?$DUSK
What I found interesting in Phoenix is that it also tries to make transactions harder to connect.
Phoenix uses notes stored in a Merkle tree. Each note has its own note public key.
Instead of using the same public key again and again Phoenix creates a one time note public key for each note.
That stood out to me because reusing the same identifier could make it easier to connect different transactions to the same user.$GRASS
The whitepaper says this one time key is designed to provide unlinkability between transactions.$UAI
There’s another part I found interesting.
The recipient can use a view key to check whether a note belongs to them while the secret key needed to spend that note can only be derived using their full secret key.
So the privacy idea here isn’t simply hide everything.
It’s more about controlling what can be connected publicly.
That made me look at Phoenix differently.
A private transaction is one thing.
Making it harder for someone to look at several transactions and connect them together is another.
And honestly that second part might be just as important.
Sending every blockchain message to everyone sounds safe. It also sounds incredibly wasteful.
That’s what made Kadcast interesting when I went through Dusk’s whitepaper.
Dusk uses Kadcast to broadcast blocks transactions and consensus votes. Instead of simply flooding every neighboring node with the same message Kadcast organizes nodes using ideas from Kademlia.
Each node keeps routing information grouped into buckets based on the XOR distance between node IDs.
Then the propagation gets more selective.
A node forwards a message to selected peers at increasing XOR distances. Those peers continue the process creating a structured cascade across the network.
Kadcast also uses multicast trees. A message starts with nearby peers which then pass it toward nodes farther away in the network. This lets the network cover its nodes with fewer relays instead of repeatedly sending the same information through unnecessary paths.$TUT
That distinction caught my attention because blockchain networking can become expensive when every node keeps forwarding everything to every neighbor.
The point isn’t just making messages move quickly.
It is reducing redundant transmissions while maintaining reliable and timely propagation.
I like this because it shows that blockchain performance isn’t only about consensus or block production.$PUMP
The network has to move information efficiently too.
Sometimes the smarter design isn’t sending more messages.
It’s knowing which nodes actually need to receive them.
The market is bringing some interesting names again. $TRUMP $BEAT Both are getting plenty of attention on the chart. At this point I’m just trying to figure out how everyone finds these moves before I do.
I used to think a failed smart contract call was basically just an error.
But the more I looked at DuskVM the more interesting the failure path became.
Before execution gets underway Dusk checks things like the sender’s balance signature and nonce. If those basic conditions fail the transaction doesn’t get to execute normally.
But what happens when something goes wrong during execution?
That’s the part I find more important.
A smart contract can make state changes while running but a failed call doesn’t simply leave those changes sitting there. The state changes from that failed execution are not committed.
So you don’t end up with a contract stuck halfway between its old state and an incomplete new one.
Gas matters here too. Contract execution consumes gas which means failure isn’t just about whether the final result was successful. There are still execution resources involved along the way.
That made me rethink what safe execution actually means.
It isn’t only about making successful transactions work.
It’s also about having predictable behavior when execution fails.
For financial applications that distinction matters. A system handling valuable assets needs to know what happens when the expected path breaks.
Sometimes the most important part of a smart contract isn’t what happens when everything goes right.
The charts are getting harder to ignore.$HEMI $ONG $ENA
Three names making some serious noise.
And somehow I’m still sitting here thinking Maybe I should’ve been watching these earlier.
One thing that stands out about TermMax Alpha is how clearly it defines the downside before a position begins.
In Alpha a Long position means buying a call while a Short position means buying a put.
In both cases you pay the premium upfront.
And that premium is what TermMax calls Max Cost the upfront amount paid and the maximum possible loss of the position.
That creates an interesting way to think about options.
You can be wrong about the market direction. The position can lose value. But you already know the maximum amount you can lose before entering the trade.
There’s no need to guess how large the downside could become.
The risk is defined from the beginning.
That doesn’t remove market risk of course. It simply makes the downside easier to understand.
And that’s the part I find interesting about Alpha.
The product isn’t only giving users exposure to a potential price move.
It also gives them a clearly defined cost for taking that exposure.
For me that changes the question from How much could I lose? to Am I comfortable with the maximum cost before I enter?
That distinction makes options much easier to evaluate.