CRYPTO NEWS

XRP’s mini breakout faces bear pressure as bullish momentum fades

  • Ripple reported a 50% jump in XRP sales in the second quarter

  • The token has pushed above a consolidation channel, but buyer power is weak

  • Investors should watch price action at $0.37

Ripple XRP/USD has seen an unprecedented demand lately. A recent report indicated that Ripple sold $409 million worth of XRP tokens in the second quarter. The sales were double that of the previous quarter. That suggested an increase in its On-Demand Liquidity service. The increase in demand could be attributed to investors’ expectations of a price surge. That relates to potential positive outcomes from the case with the SEC.

Despite the second quarter sales, XRP remained in the trenches. It held to a bottom of $0.3 up to mid-July. Ripple attributed the low price of XRP to macro issues and protocol-specific developments. Of course, notwithstanding, the SEC case could go either way.

Still, investors have been optimistic about XRP price recovery. After the price remained in a consolidation zone for nearly 2 months, it broke out on July 30. The breakout occurred after the price pierced through the $0.37 resistance. However, we see this as a mini-breakout as the token has to overcome another tackle at $0.40. That explains why bulls’ power remains weak. However, XRP remains on course for stronger gains and should be on investors’ watch list.

XRP retreats to resistance-turned support after the latest breakout

Source – TradingView

On the daily technical outlook, XRP has touched the $0.37 breakout level after the latest correction. The MACD indicators are bullish on the token, although the momentum is waning. Investors should watch $0.37 for a potential bullish reversal. If XRP breaks below the level, it could slip back to the consolidation zone once more.

Summary

XRP remains in bullish momentum, but bears are pushing the price lower. We need to watch $0.37 for a bullish reversal.

The post XRP’s mini breakout faces bear pressure as bullish momentum fades appeared first on CoinJournal.

Retrieve Storage Variable Name given Storage Location and Contract Source

Is there any easy way to get the storage variable names provided you have the source code and the storage locations of the variables for a contract? For example, for the following contract I can use solc AToken.sol –storage-layout to obtain the storage layout, which would look something like this: { "storage": [ { "astId":::Listen

Is there any easy way to get the storage variable names provided you have the source code and the storage locations of the variables for a contract? For example, for the following contract I can use

solc AToken.sol --storage-layout 

to obtain the storage layout, which would look something like this:

{   "storage": [     {       "astId": 2353,       "contract": "AToken.sol:AToken",       "label": "lastInitializedRevision",       "offset": 0,       "slot": "0",       "type": "t_uint256"     },     {       "astId": 2356,       "contract": "AToken.sol:AToken",       "label": "initializing",       "offset": 0,       "slot": "1",       "type": "t_bool"     },     {       "astId": 2426,       "contract": "AToken.sol:AToken",       "label": "______gap",       "offset": 0,       "slot": "2",       "type": "t_array(t_uint256)50_storage"     },     {       "astId": 1584,       "contract": "AToken.sol:AToken",       "label": "_balances",       "offset": 0,       "slot": "52",       "type": "t_mapping(t_address,t_uint256)"     },     ... 

So given a list of storage location hashes e.g. 0x0000000000000000000000000000000000000000000000000000000000000036, etc. I can use

web3.utils.getStorageAt('0x7b2a3CF972C3193F26CdeC6217D27379b6417bD0', storage_location_hash) 

to obtain the value of a given slot for the contract. I can easily discern the variable names of simple variables, like uint256 type – 0x36 is just 54, which tells me the slot number and corresponding variable name. However, storage hashes such as 0xe508bcfa121f037568ba66d134df0df9a711886af8fe244fd9c8cb7cfc1d050c are more complicated to match with their corresponding variables, and I’m unsure how to discern which storage variable these refer to. My guess is they refer to more complicated storage types like mappings().

The only way I can think of to extract the storage variable name for these variables is to attempt to bruteforce different combinations of inputs to web3.uitls.soliditySha3(), e.g. web3.uitls.soliditySha3({type: ‘uint’, value: 6}) would give me the storage hash of the first element in an int array in storage variable slot 6, but this seems extremely inefficient and a roundabout way of doing things. I would hope that a simpler solution exists that I’m just missing.

To summarize: I’m looking for a solution that retrieves the storage variable name provided I have the storage locations and the contract source code

XRP’s mini breakout faces bear pressure as bullish momentum fades

Shopping cart
There are no products in the cart!
Continue shopping
0