Jump to content

rippleHero

Member
  • Content Count

    29
  • Joined

  • Last visited

Reputation Activity

  1. Like
    rippleHero reacted to FOOD in What does it mean to activate an address?   
    You have so many questions that I can not answer... beyond my technical knowledge... but I can not help but recognize the irony of your user name... to me, it implies a level of expertise beyond what most could comprehend.... or perhaps this is what  you aspire to become? 
    Unless, of course, you are using the other meaning of the word "hero", which is "submarine"...  but if so, why?
  2. Like
    rippleHero reacted to BehindtheLedger in Can issuing OfferCreates of XRP push up the price of XRP?   
    Incorrect. Unfilled orders do not create volume. 
  3. Like
    rippleHero got a reaction from bestfreeshare2013 in Can issuing OfferCreates of XRP push up the price of XRP?   
    Right @Chris_Reeves so if you wanted to create fake volume, creating offers and then canceling them would work. But the fact that you create an offer would not push up the price? (Unless you execute/fulfill the order).
  4. Like
    rippleHero reacted to MemberBerry in Who receives the XRP that Ripple distributes?   
    Programmatical sales is a nice word for "ripple is dumping xrp"
    😂
  5. Like
    rippleHero reacted to BobWay in Answer: How to decipher specific ripple transaction?   
    @Sukrim have you ever seen a transaction like this. Not the path. But a payment that succeeded without moving funds?  I would expect it to be tecPathDry in most cases. The partial payment flag might preclude that by declaring that zero USD is a partial payment. I'm stumped.  
  6. Like
    rippleHero reacted to Sukrim in Answer: How to decipher specific ripple transaction?   
    I asked for an internship next to my studies a few years back, they responded a few months later that they lost my mail and now have selected interns already. These days I'm not sure if I want to live in the US and I haven't ever heard back from my inquiry if (mostly) remote work from the EU would be ok for them.
    I'll take another look at this transaction and transactions like it, I never really got around to implement the transaction analysis tool I wanted/started to build. Definitely a slightly weird outcome, reducing 2 open offers like that.
     
  7. Like
    rippleHero reacted to King34Maine in Who receives the XRP that Ripple distributes?   
    You can search transactions via the XRP Charts Account Explorer. I don't have time to go through everything check out this previous discussion as it might give you some clarity: 
     
  8. Like
    rippleHero reacted to Sukrim in Answer: How to decipher specific ripple transaction?   
    How would one actually get in contact with them though and what do they want, proposal wise? "I propose to build a proper web interface for visualizing transactions properly for XX.XXX USD, here's my bank account!" probably won't fly I guess, on the other hand this stuff is impossible to monetize (yes, even with Coil existing).
    https://developers.ripple.com/transaction-formats.html - There's plenty of information...
    https://xrpcharts.ripple.com/#/transactions/49522DFAD0A35174663285BD6149437C3D4F2B6F1456E33C26129332915981D7 took out the fee from the sending account and just decreased amounts on an open offer in an order book by the same user. Looks a bit funny though, but in essence the user said "I want to convert some of my CNY to USD" while having offers for both currencies open, so it just reduced the amounts of these offers accordingly instead of having to actually trade on the market. Issuing a payment to yourself is just a way to automatically trigger pathfinding.
  9. Like
    rippleHero reacted to BobWay in Answer: How to decipher specific ripple transaction?   
    This payment path starts in XRP, uses STR as a bridge currency, then ends up in XLM. It goes though the XRP/STR market and then through the STR/XLM market.
    Rome describes it. But he does not put the results in path order either. I swapped them below.
    It modified a XRP/STR Offer node of rGMNHZyj7NizdpDYW4mLZeeWEXeMm6Vv1y
        The offer's Sequence number is 293916.
        the offer was partially filled.
        TakerPays decreased by 67.85405700000001
        from 232.57633 to 164.722273 XRP
        TakerGets decreased by 231.990345952928
        from 795.16931 to 563.178964047072 STR.~mrr (rB3gZey7VWHYRqJHLoHDEJXJ2pEPNieKiS)

    It modified a STR/XLM Offer node of rMxkau5LJiidEk1S9X8RxxnX1uCx1zryvb
        The offer's Sequence number is 119367.
        the offer was partially filled.
        TakerPays decreased by 221.63955258639703
        from 1,585.0945 to 1,363.454947413603 STR.~mrr (rB3gZey7VWHYRqJHLoHDEJXJ2pEPNieKiS)
        TakerGets decreased by 224.13924600000018
        from 1,602.9715 to 1,378.832254 XLM.~ripplefox (rKiCet8SdvWxPXnAgYarFUXMh1zCPz432Y)
     
  10. Like
    rippleHero reacted to BobWay in Answer: How to decipher specific ripple transaction?   
    Bithomp isn't giving you the REALLY RAW data that rippled does. Bithomp has parsed and reformatted it to make it easier to follow. I could give them some hints on making it even easier though. 
    Let's use Bitthop's for simplicity, but notice that Bithomp (probably accidentally) left out the destination amount the payment was intended to deliver. That makes these RAW results slightly opaque about the user was attempting to do.
    But if you lookup to the top of the bithomp web page, you see they did put it there.
        Delivered amount:321.460719 XLM (Ripple Fox)
    It delivered 321.460719 so that must have been related to what the transaction was trying to do.
    ----
    You can also look at that transaction this way. Thank Rome Reginelli for that beautiful hack. 
    https://xrpcharts.ripple.com/#/transactions/1A06B8E85C40B3756BE0B24A04DEE76E5BC5B0EFFBABB15F4634860CA78807F4
    Let's let Rome tell us what this transaction was trying to do.
        DESCRIPTION:
            This is a Payment transaction.
            The payment is from rsdMbYxHmYswHCg1V6vBsnxmHuCjpn6SC4 to rsdMbYxHmYswHCg1V6vBsnxmHuCjpn6SC4.
            It was instructed to deliver 321.46072 XLM.ripplefox (rKiCet8SdvWxPXnAgYarFUXMh1zCPz432Y) by spending up to 100 XRP.
            The actual amount delivered was 321.46072 XLM.ripplefox (rKiCet8SdvWxPXnAgYarFUXMh1zCPz432Y)
            The transaction's sequence number is 566
    Brilliant!
    FLAGS:
        The transaction specified the following flags:
            tfNoDirectRipple
            tfPartialPayment
            tfLimitQuality
    The last two flags are important. They mean give me as much as you can, but only what's available at a favorable price. These and the circular nature of this payment, tell me the sender was trying to take advantage of some bad pricing along the path in order to get a good deal on Lumin. I don't have his next transaction, but I would be he converts that XLM back to XRP and ends up with more XRP than he started with. If so that represents circular arbitrage. If not, the sender just wanted a good price on XLM.
    If you switch to the RAW tab, you can see the even more complicated version that rippled returns. No wonder bithomp wants to simplify it right?
    ----
    The key to figuring it out starts by first understanding what was rippled asked to do. That is what the specification sub-object is for.
        "specification": {
        "source": {
            "address": "rsdMbYxHmYswHCg1V6vBsnxmHuCjpn6SC4",
            "maxAmount": {
                "currency": "XRP",
                "value": "100"
            }
        },
    Specifically, inside that you need to decode the path that ripple was asked to take through the Ripple ledger graph.
        "paths":  
            "[
                [
                    {    
                        "currency": "STR", 
                        "issuer": "rB3gZey7VWHYRqJHLoHDEJXJ2pEPNieKiS", 
                        "type": 48, 
                        "type_hex": "0000000000000030"
                    }, 
                    {    
                        "account": "rB3gZey7VWHYRqJHLoHDEJXJ2pEPNieKiS", 
                        "type": 1, 
                        "type_hex": "0000000000000001"
                    }, 
                    {    
                        "currency": "XLM", 
                        "issuer": "rKiCet8SdvWxPXnAgYarFUXMh1zCPz432Y", 
                        "type": 48, 
                        "type_hex": "0000000000000030"
                    }, 
                    {    
                        "account": "rKiCet8SdvWxPXnAgYarFUXMh1zCPz432Y", 
                        "type": 1, 
                        "type_hex": "0000000000000001"
                    }
                ]
            ]"
    The "path" array, there can be many inside the "paths" array, here has only a single path so that make my explaination easer. But the path represents only the middle section of the path. To that you need to add the source and destion endpoints around the path.
        "destination": {
            "address": "rsdMbYxHmYswHCg1V6vBsnxmHuCjpn6SC4"
        },
    Please note:
                        "type": 48, 
    means you want to go through a orderbook
                        "type": 1,
    means you want to ripple through the specified party

    Notice the source and distination are the same so this payment path represents is an attempt as circular arbitrage.
    Also I see these two flags set. This tells me this transaction is an attempt to arbitrage bad pricing somewhere along the path. "allowPartialPayment" means
            "allowPartialPayment": true,
            "limitQuality": true

    That gives you the end-to-end graph of the parties involved. Then you draw a graph of that in the notation I haven't showed you yet. But it is very similar to the Ripple graph explorer on the XRP Charts section of the Ripple website. 
    This is the source address and all its trust line relationships to other parties. If you hover over those counterparty circles you can see there addresses as well. If you double click ones with an outscribed circle, they'll expand to show you their trust lines as well.
    https://xrpcharts.ripple.com/#/graph/rsdMbYxHmYswHCg1V6vBsnxmHuCjpn6SC4
    Unfortunately the browser is a bit frustrated by the fact that XRP isn't accounted for using trust lines, so it can't draw the complete graph. The notation I use, treats XRP as a trust line to a single XRP issuing entity (representing the ledger itself). If you do that, the transaction path becomes much easier to follow.
    https://xrpcharts.ripple.com/#/graph/
    rB3gZey7VWHYRqJHLoHDEJXJ2pEPNieKiS

    Once you have the graph drawn out, and only then for me, do you begin to approach understanding what rippled ACTUALLY DID in processing your request.
    The resutls of transaction request are specified in the outcome sub-object. 
        "outcome": {
             "balanceChanges": {
       
    This specifies every balance that rippled updated. This includes both trust line and XRP balances. Unfortunately, these are not in path order, which is why you need your hand drawn graph.
            "orderbookChanges": {
    This specifies the changes to the markets that executing the payment caused. Bithomp has formatted this better than rippled, but like rippled the results are not in path order. So you need your paper graph even more.
    It turns out, the results are probably easer to follow using Rome's parsed version.
    I'm not going to finish the analysis because my head hurts, and I spent time typing all this up rather than drawing the path graph like I should have.
    But this should get you started.

     
  11. Like
    rippleHero reacted to retryW in Answer: How to decipher specific ripple transaction?   
    Bithomp is great for looking at regular txs, but for complex ones not so much.
    On XRPCharts you can see this is a tx completing a DEX orderbook
    https://xrpcharts.ripple.com/#/transactions/1A06B8E85C40B3756BE0B24A04DEE76E5BC5B0EFFBABB15F4634860CA78807F4
    DESCRIPTION: This is a Payment transaction. The payment is from rsdMbYxHmYswHCg1V6vBsnxmHuCjpn6SC4 to rsdMbYxHmYswHCg1V6vBsnxmHuCjpn6SC4. It was instructed to deliver 321.46072 XLM.ripplefox (rKiCet8SdvWxPXnAgYarFUXMh1zCPz432Y) by spending up to 100 XRP. The actual amount delivered was 321.46072 XLM.ripplefox (rKiCet8SdvWxPXnAgYarFUXMh1zCPz432Y) The transaction's sequence number is 566 MEMOS: The transaction has no memos. TRANSACTION COST: Sending this transaction consumed 0.000012 XRP. FLAGS: The transaction specified the following flags: tfNoDirectRipple tfPartialPayment tfLimitQuality  
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.