Expert Debunks Securities Assumptions for XRP Price Forecasts

Shannon Thorp, a Treasury Management expert at a major global bank, discussed divided opinions within the XRP community about price outlooks.

In a Twitter thread, Thorp highlighted some reliance on Bitcoin-linked charts for short-term XRP predictions, while utility-focused believers anticipate partnerships driving the price.

Importantly, she pointed out XRP is not a security, questioning the logic of basing crypto price forecasts on securities frameworks. Thorp suggested clinging to such notions hinders Ripple’s original mission.

Her comments shed light on contrasting XRP price philosophies – short-term technical traders versus long-term utility and adoption proponents. She challenges applying securities assumptions to XRP, which she asserts was created for pragmatic cross-border solutions.

The thread illustrates ongoing debates within the XRP community about divergent price modeling approaches and interpretations of XRP’s status and purpose.

When asked for a price prediction, Thorp noted uncertainties around timeframe, supply, and baseline dollar amounts. She referenced recent developments like the SEC ruling, FedNow, and proposed crypto regulation.

For a short-term estimate, Thorp suggested $100-$500 based on liquidity calculations where higher prices allow growth without monopolization for everyday uses. She argued narrower ranges like $1-$5 have problems.

Thorp hypothesized a scenario of a large $750 million transaction at $1 liquidity. This would account for ~10% of XRP held by banks, requiring breaking it down into multiple smaller transactions with burn rates – potentially impractical.

Her point is higher liquidity pricing allows major transfers without dominating supply. She cautions against tightened XRP price ranges that could constrain institutional settlement liquidity. While short-term technicals suggest lower prices, utility considerations warrant higher runway.

#Thorp #XRP #Bitcoin #Securities

Leave a Reply

Your email address will not be published. Required fields are marked *