Jump to content


  • Content Count

  • Joined

  • Last visited


About josepi90

  • Rank

Recent Profile Visitors

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

  1. also worth reading this.. https://hackernoon.com/the-6-costliest-mistakes-people-make-when-trading-bitcoin-otc-d975d4acda25
  2. Think his exact quote was " Diversification is for people who dont know what they are doing"
  3. Video also now featured here, https://ripple.com/sbi-ripple-asia/ (perhaps old news ? but could not find anywhere on the forum..)
  4. HI, This video presents the SBI "Ripple Connect" cloud partnership, showing ILP usage in the animation..in Japanese (with intermittent subtitles) just uploaded to youtube. screenshot from the end of the video showing participants,
  5. Thanks good to know - not so easy to explain network protocol stacks in a forum, but to simplify for non technical readers, just understand that for each ILP packet being sent, the transaction info/wallets addresses etc are enclosed inside a TCP header ( think of this as an envelope with ILP transaction info inside), The address on the outside of the "envelope" shows IP and TCP information used for routing the "envelope" between servers over the internet (IP) , and making sure its been received without being corrupted and is handled by the correct process (TCP). RFC is below for those looking for more technical info. Ledger layer currently is generally using TCP443( https) as far as i can find, but does not have to be and can be defined on a use by use case according to the RFC. Also found a more official discussion on the idea in my earlier post https://github.com/interledger/rfcs/issues/146 https://github.com/interledger/rfcs/blob/master/0001-interledger-architecture/0001-interledger-architecture.md
  6. IP will always be required as the layer 3 protocol, required for addressing for end nodes(hosts/servers), and to provide & calculate routing information for packets flowing around the network. TCP is a layer 4 "protocol" ( TCP being "connection orientated", meaning both nodes confirm receipt of all data, ) with RIppleD using ssl ports 443 i believe. Theoretically DLT data ( XRP/ILP ledgers etc) could be setup to run using their own layer 4 ports/sockets, but this would require all internet routers to have a new version of their operating systems implemented - it would mainly result in smaller packets of data being switched around, reducing processing and increasing speed of the network (again in theory). Very unlikely to happen, through largescale adoption of IPv6 might be the time where this could be looked at being implemented, assuming huge global use of the ledgers would drive the concept forward. These 2 presentions are a good source for more details on the specs of the ILP standard https://www.w3.org/2017/Talks/ilp-commerce-20171110.pdf https://interledger.org/presentations/2016-07-06 - ILP Workshop London 2016.pdf
  7. Thanks. Good times indeed.. at the same time my employers were spending 100's of millions on Cisco hardware annually.
  8. I wrote this a few weeks ago for the xrpcommunity blogsite -somewhat related https://xrpcommunity.blog/ripple-will-be-the-cisco-systems-for-the-internet-of-value-a-k-a-memoirs-of-young-network-engineer-circa-1986/
  9. fyi cross-border payments are very briefly mentioned at 1:16:20
  10. according to Wikipedia "The Committee also oversees the work of the Federal Reserve, the United States Department of the Treasury, the U.S. Securities and Exchange Commission, and other financial services regulators
  • Create New...