Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by ScottBranson

  1. While I am very sorry for people's losses, I adamantly oppose using our validator to censor or alter any transactions, as doing so would surely have substantial negative effects for the overall XRPL. As @alloyxrp already observed, this is a slippery slope indeed! Further, it isn't even possible or practical, as there are so many default UNL validators that would surely disagree with this course of action. Irreversible theft is a consequence associated with decentralized systems, and I personally avoid keeping any value on exchanges, as I see them as rather large targets for theft.
  2. How is that not democracy? In a democracy people are free to defend or support other's decisions. It seems like you think a democracy involves people doing what you think they should do, instead of letting them choose for themselves. Anyhow, this conversation seems fairly pointless to me. I told you my opinion on the wallet reserve and enabling amendments. You haven't presented a single compelling reason for me to change my views, you just keep complaining that people aren't doing what you want On that note, I'm off to bed. Nighty night.
  3. I guess that's how democracy works - everyone is free to choose who to trust, follow, etc.
  4. Then just fork the rippled Git repo and make your own UNL. If enough people don't like what Ripple is doing, surely they will follow. Again, this is democracy.
  5. It sounds like you want to have things exactly how you want them, which isn't democracy. Perhaps what you don't like about the Ledger is that it is democratic?
  6. If people don't like how Ripple's validators' vote, then they could choose to stop trusting those validators entirely. How is that not democratic?
  7. I'm not sure how you define democratic, but in my view the Ledger is a democratic network. In your response you say that most of the validators are voting for the Checks amendment. If it isn't democratic, why are they voting? Amendments have serious implications for the network, which could have irreversible consequences. Thus, I believe they require thorough testing prior to implementation. This view is arguably reflected in the fact that amendments require 80% support from the voting quorum to pass. For this reason, our validator, which is included in the default UNL, is currently vetoing the checks amendment. I plan to change this to vote in favor of the Checks and FlowCross amendments in the relatively near future, as they have been fairly well tested without issues on the TestNet. There are other default UNL validators that are not run by Ripple that are actively vetoing these two amendments, possibly for the same reason. As a default UNL validator operator, I see it as imperative that I act slowly and intentionally with things like amendments and fees, so I can do my absolute best to be a good steward. It is easy to talk about making changes, but my aim is to prevent unforeseen consequences.
  8. If you were the only validator voting to lower the fee, then perhaps there is a reason the other validators disagree with you, like the reasons I stated. You haven't given me any compelling reason why fees should be lowered, so I see no reason to change my vote based on this discourse. This isn't true. All the validators could set different values, which would result in a compromise. More info on how voting works here: https://developers.ripple.com/fee-voting.html
  9. I think it is perfectly acceptable, as the wallet reserve is explicitly designed to prevent spam. Creating wallets is particularly onerous for full history nodes, and it is expensive to run a full history node. If you don't like it, you are welcome to spin up a validator, gain trust and reputation, and vote to lower the fee. It is a democratic network, after all
  10. I don't see this as a relevant comparison, as these assets are all distinctly different with regard to history size, average tx/ledger, etc. ETH miners are incentivized, so spam is arguably less relevant to them. Different cryptos/tokens/assets have different use cases, which result in different fee structures, etc. I totally understand the frustration with the wallet reserve, and, like I said, I think there is great value in making XRP accessible while also balancing the overall ledger size. For people who can't afford the wallet reserve, I hope they will still use apps that allow them to transact using XRP, like the XRP Tip Bot (which is a terrific solution to this issue, IMO). Anyone who doesn't like the wallet reserve should encourage exchanges, like Poloniex, to stop creating a wallet for every user, and instead use destination tags. This eliminates the need for exchange users to have a wallet reserve, while also reducing the Ledger's overall size.
  11. On the other hand, I don't think it makes sense to assume that an amendment to delete accounts that may or may not even be coded will exist. There is a balance between making XRP accessible to people and ensuring the ledger size stays manageable. We also need full history nodes, and they will have to store everything associated with deleted accounts.
  12. The object will still be an issue for full history nodes.
  13. Ms. Rabbit and I very much agree. When considering what the account reserve should be, please keep in mind that people who run rippled nodes are essentially donating storage space (9+TB for a full history node) as well as bandwidth (one of our nodes used >1.3TB in bandwidth just yesterday) and memory. You may have 20 XRP (~$10) in reserve, but that account lives on the ledger for ever, and nodes have to pay to store it indefinitely (at least until an amendment allowing accounts to be deleted passed). Even if the account can be deleted, full history nodes still have to store the account's history. Further, exchanges like Poloniex needlessly create new accounts for each user, instead of using destination tags. This causes a tremendous amount of needless pollution. The wallet reserve is designed to prevent spam (i.e., people creating more accounts than they need), and, last I checked, Polo is still needlessly spamming the ledger. If anything, this suggests the reserve is too low. For these reasons, we have no intention to change our vote regarding the reserve at this time. @Tinyaccount is right, though, us greedy validators love sucking XRP from noobs
  14. Session 1 works for me. Thanks for organizing this!
  15. I wonder about keeping it as simple as possible, then - use Zoom for live video calls, then post the recordings to YouTube. Links to videos and Q&A can then happen in XRPChat. The main benefit of Moodle would be having a permanent course shell where you can organize information easily in sequence in one place (e.g., if you are planning to upload information in multiple formats- zoom videos, word documents/pdfs, readings, glossary of key terms, quizzes, surveys, live chat, etc.) However, this may not be needed.
  16. We can set Moodle up for you and admin it, if we decide to go that direction. I looked at the requirements for Moodle and it looks like a pretty straight forward PHP app that runs on a LAMP stack. I would volunteer server space (assuming we don't need like a massive server) and could sys admin the LMS. Ms. Rabbit is willing to help with the actual course design and organization, as her university uses Moodle. It looks like we would still need some sort of a Zoom or other video conferencing account. It looks like Zoom allows up to 50 users, and videos can be streamed to Moodle, YouTube, and other platforms. I'm not 100%, but it looks like room.sh limits video calls to 6 participants max.
  17. Hi Bob, Based on what you are describing, my wife suggested using a learning management solution like Moodle. She uses Moodle for teaching her online and hybrid courses. There are plugins for Zoom, WebEx Meetings, H5P interactive video content, text based chat etc. and the platform allows you to break down content by topic/week. It could be one way to help keep everything organized. Thoughts?
  18. Hello all, I'm rabbit. I live in Michigan, USA (EST/EDT), I work as an assistant professor (unrelated to IT/CE/CS/etc.), and I only speak English. I am married to Ms. Rabbit, who used to share this XRPChat account with me. My aliases on other sites include: Website: rabbitkick.club Twitter: @RabbitKickClub Git: crypticrabbit Youtube: rabbit XRPCommunity.Blog: rabbit reddit: RabbitKickClub Out of those, I basically only use the Twitter, since I can't keep up with everything . My background with Ripple/XRP includes using Ripple Trade when that was around. I really miss having easy access to features like adding gateways, enabling rippling, etc., and one of my primary aims in joining this group is to learn more about utilizing all the awesome features to their full potential, so more people can benefit from them. I have been running rippled for the last several years, and I'm honored that our validator is included in the default UNL. I love learning new things, and running rippled has taught me a great deal. Out of the roles that @BobWay proposed, I see myself ideally being involved in the live audience. I look forward to being a part of this group! Cheers, rabbit
  19. Thanks to everyone for all of the support and encouragement. I'm honored to be selected alongside someone as awesome as Wietse (@xrptipbot), particularly given the incredible ways that he contributes to the community as well as the broader XRP ecosystem.
  20. ^^ That is a great site. @jn_r also posted JS to parse vl.ripple.com here: https://www.xrpchat.com/topic/24595-validator1worldlink-uscom-makes-it-to-ripples-recommended-validator-list/?tab=comments#comment-437973
  21. As of today, Ripple is carrying on with their decentralization plans. They have now added two non-Ripple validating nodes to their recommended UNL: Worldlink-US and Flagship Solutions Group. Consistent with their strategy, they have removed one ripple.com validating node. Even before decentralization started, it would have been possible for independent nodes to over rule Ripple's validating nodes, as they were vastly outnumbered.
  22. You make wonderful points about the importance of online diversity, and I agree. I'm worried that, without substantial oversight/regulations, all pay to play systems ultimately become concentrated among a small number of massive players. I'm personally more bullish on a solution that entirely (or at least largely) eliminates ISPs. To be clear, I think that, while intriguing, streaming payments for bandwidth promotes the same closed internet as ISPs are now permitted to build.
  23. This is deeply concerning to me, and I do hope that we see some sanity from Congress, although sanity there seems like a long shot. I've come across a few news articles on p2p/mesh networks, that seem promising w/ regard to developing a system around many ISPs, although they still rely on backbones, at least for now.
  24. This is an interesting question, @Mercury, and one that I have also been thinking about, particularly in the context of metered utilities. For example, electricity, gas, and internet could all work on ILP to debt payments for services as they are used, and utility companies could be paid live. I pay for a relatively fast internet connection, however, I rarely require the full bandwidth that I can access. It seems like it could be beneficial for me pay for the actual bandwidth that I am using, as opposed to the current model when I pay for the maximum possible speed. At the same time, how many toll points would there be? Would every router operator be able to charge a toll? Would larger ISPs be able to out compete others, forming a relative monopoly that is capable of censoring the internet? I have to imagine the ISPs with the most infrastructure would be able to charge lower rates, and people would prefer using the cheapest routes. I do worry about the threat that net neutrality poses to a number of different services. I could see ISPs claiming they are justified in blocking XMR mining, since a surprisingly high number of apps/websites are seemingly covertly mining.
  25. I have posted a video that includes some highlights from @hammertoe's interview with Tai Zen yesterday. This (and/or the full interview) is a must watch for anyone who wants to better understand the XRP ledger!!!
  • 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.