Jump to content

devnullprod

Member
  • Content Count

    135
  • Joined

  • Last visited

2 Followers

About devnullprod

  • Rank
    Regular

Contact Methods

  • Website URL
    http://wipple.devnull.network

Profile Information

  • Gender
    Male
  • Location
    Upstate NY
  • Ripple Address
    rhkvfNv6tzh6CMfpXZdX2t7HGN2ZX46Tco

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks for the feedback @Flintstone! Will address those alignment issues momentarily (and agree, will also add a link to the main site nav)
  2. Come one, come all, hear the announcement of Wipple 0.13.1!!! For those who don't know Wipple is a ledger monitor and analyzer, aimed at providing users with simple tools to retrieve deep ledger insights as well as perform useful functions on the network. This release brings many new features and improvements including streamlined navigation, extended tools which to highlight and filter transactions, a widget to view a timeline of account transactions (expiremental), as well as much needed backend hardening and testing. The reporting UI has been expanded to support viewing of higher order timeframes and we've gone through the application and improved the mobile experience, so all sections are accessible via smartphone / tablet interface. Be sure to checkout our newly launched blog for the complete details and don't wander far away, we've got many more features planned for the next release which is just around the corner! Happy rippling!
  3. We're working on some XRP analytics tools: https://wipple.devnull.network/ Not free software (yet) but perhaps there's some room for synergy / collaboration. Let us know if your interested (here or via devnullproductions@gmail.com)
  4. Awesome, no sweat, the beauty about being to the game this early is there are so many possibilities for implementations. They way we see it is it doesn't even matter if there is some overlap in feature sets between sites, different users have different preferences and will be drawn to different platforms and interfaces. We each just have to doing our own awesome thing and the entire ecosystem will benefit as a whole (including increased adoption of XRP). As features shore up and developer interest becomes more concrete different groups can come together and collaborate in different ways. Definitely looking forwards to seeing what you'll produce, keep us posted!
  5. We're doing something similar (deep ledger analysis): http://wipple.devnull.network/ Shout out (here or private message) if you're interested in collaborating.
  6. @Sukrim yet again you saved the day! (do you have a xrptipbot address, if so a tip is heading your way!) According to the docs metaData.TransactionIndex is the tx position in the live ledger, so we just need to sort on that: https://developers.ripple.com/transaction-metadata.html
  7. Today just doesn't seem to be my day! While tuning and verifying our db I noticed a particular situation with some ledger traffic that seemed to trip up our synchronization system. The incident which we noted was in ledger 45263657 particularily with the two transactions originating from "rQK6HjFraXpWo4RiKKjuumrnrZpTFDtbAX". https://wipple.devnull.network/live/ledgers/45263657 This particular case is a bit strange because they appear in the transaction log appearingly out of order (Sequence 109 is before 108), the later is right after the former, and the former deletes a RippleState object which is modified in the later. It is our understanding that if a transaction comes in out of order rippled will hold onto it for a while or until the sequenent missing transactions comes in, so perhaps this is the case there, but my question is why the transaction list in the ledger would not be sorted by final transaction application order? Also how can one reconstitute this order for use of tracking changes locally. Thanks again!
  8. @Hodor awesome, great to have your support! I'll put this out there, if we can find an artist that would be willing to do the final illustrations, we'd be willing to build and host the site, and even storyboard it if need be. Agree that this would work best as a easy-to-find / navigate independent sort of thing, where you can give the link to someone and they can easily click through like a book.
  9. @Flintstone definitely! Though would have to say that level of detail would be more suited for an involved technical guide where the consumer is at least an acquainted end user, already familiar with the basic concepts. The concept that I was thinking about would moreso be a handful of pages (or perhaps 'panels') mostly constituted of comic-like content, which would start with general economic trade & banking concepts that most adults can grasp and eventually evolve into the top level features of XRP and what it brings to the table. Something you could show to your grandparents who are acquainted with writing checks and perhaps wiring money / using western union, and use that knowledge to help them understand the XRP 'brand'.
  10. Ahhh it was so simple all along! The obvious was right infront of us, converting to an int via base58 & the ripple alphabet resulting in the correct sorting. Thank you for the quick response! We're going to grab another cup of coffee!
  11. Good day! Apologies if this question has already been asked but I wasn't able to find the answer anywhere in the documentation / support. According to the documentation, Balances and TrustLines in the ledger are represented though 'RippleState' objects which record the two accounts associated together along with a balance: https://developers.ripple.com/ripplestate.html Looking at the example RippleState JSON provided, this doesn't seem to be as described as the "HighLimit" corresponds to "rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpn" and the "LowLimit" corresponds to "rsA2LpzuawewSBQXkiju3YQTMzW13pAAdW". This doesn't make sense as ascii / unicode table assigns 0x66 to "f" which is lower than the 0x73 assigned to "s". Thinking about it, I next thought that perhaps accounts were sorted in accordance to the ripple alphabet: Which would make sense in the above example but if we look at another one, this does not hold up. Here we see the "HighLimit" is "r9g5TLjM4P9ijgAAVVsf8KDPWSroeHjE4q" and the "LowLimit" is "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B" which wouldn't be correct in either the ascii or ripple-alphabet sorting schemes. Could someone please elaborate exactly how addresses are numerically assigned such that they are ordered in the manner described above. Thank you greatly.
  12. Talk about timing @Hodor! (great posters hit 'submit' alike!) Would love to get your thoughts, if we did manage to throw something like this together, think we could get it up on the community blog?!?!
  13. Love it! Great idea as far as demonstrating working functionality right in the documentation. Perfect use of the testnet! (Both the docs and the testnet have been an invaluable resource as far as understanding and testing the XRPL, keep up the great work!) This reminds me of another idea we were mulling about pertaining to documentation / demonstration. We were thinking of throwing together a user-friendly guide to XRP for novices / newbies, something explaining what it is at a very high level (perhaps something similar to howhttps.works or why's poignant guide but with unique artistic style / content). Perhaps this could expand upon the idea presented here and embed some user-friendly way to send payments across the testnet ("click this button"... "look you've just transferred $100 USD across the network!") Unfortunately we have too many other priorities at the moment so can't do this one justice, but perhaps if there is interest we could do this as a community effort, with a few members of the community collaborating on different fronts (an artist would be need). Whaddya think #XRPCommunity? Yay or nay?!
  14. @Sukrim @nikb I understand the concerns about brute forcing it fewer chars, etc. Unfortunately even with 7 characters or so, it's well within the realm of possibility of generating an account any given substring in a reasonable amount of time. Unfortunately this comes down to a "convenience" vs "security" situation, which as you know is always a tradeoff. I'm definetly not proposing this solution for any situation requiring any level of formal security or verification (even the most minimal), but rather just exploring this topic for the most informal of conversations, when discussing account activity via social media channels such as twitter for example (where typing out full account addresses has an adverse effects towards tweet character limits). @fluxw42 I love the identicon idea! I'm going to look at integrating this into the Account Details Page on Wipple (https://wipple.devnull.network/live/accounts/rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B) and perhaps making it accessible via an embeddable widget. Should provide a quick way to visualize accounts. Great thinking!
×
×
  • Create New...