Jump to content


  • Content count

  • Joined

  • Last visited

  1. Thanks - steffenmanden ! I have fixed, and uploaded a new verison, link also updated in the OP. Apologies for my screwup. https://docs.google.com/spreadsheets/d/1TaMd8GXppBhuFUzeHyh0ITp-QOU74jmzHVTPjWLTpkQ/edit?usp=sharing
  2. agreed. there is an error in the calculations.. i will fix now. Thanks for the heads up
  3. josepi90

    InstaReM (RippleNet Member) Launches in the UK

    according to this link xcurrent and xvia https://www.finextra.com/newsarticle/32174/instarem-and-beetech-open-payment-corridor-on-ripplenet
  4. josepi90

    InstaReM (RippleNet Member) Launches in the UK

    As they send payments to 60 countries, let's hope their really looking for the cost-effective option.
  5. I'm not a derivatives expert by any means, but above I was thinking of the contracts themselves, forwards, futures, options could all be "simple" smart contracts, bought and sold as they are now, actioned by codius at the expiration. All possible I would think, assuming trust was assured. Swaps as i ( very basically) understand them, might require a different setup. but im sure they run as code now, so could be programmed. The derivative assets themselves could eventually be on any blockchain, with ILP as the bridge, Codius being a transaction handler, XRP being the settlement asset.
  6. interesting watch.. Mayur Kapani references trading volumes on the Intercontinental exchanges at billions of usd per second, a small slice of that into derivative codius contracts would be nice.
  7. here is another link to the conference, OP links seems to be broken.
  8. Not new, but missing from list.
  9. HI, sure i will try to explain.. Calculations flow like this.. initially we set 2 variables the price of XRP ( row 17) the CODIUS_XRP_PER_MONTH setting ( row 16) around row 200 there are two tables side by side, AWS hourly fees, converted in AWS monthy fees for each service type. Later we reference the monthly fee for each service. in the same area eq row 204 we show the servers memory in GB, calculate each servers capacity, converting GB memory in MB memory, then into number of codius contracts each server can support ( xGB * 1024= xxxMB ), this divided by 512 ( each codius contract is 512 mb), give the server max contract capbility, eg AWS biggest server( x1e.32xlarge) has 3094 GB ram. this is 3997696 , so supports (3997696/512= 7808 contracts per month if 100% utiised. -- 5) At the top in the 1st table , column F we have the number from the previous step ( number of contracts). 6) Column G multiply the number of contracs by the XRP per month to calculate max XRP earnings, 7) in column Q we multiple the number of XRP earnings, by the XRP price, and then deduct the server cost from column C There are some hlookup functions that select the service type from the 10 options, and change the server monthluy charge to match ----- Also its easier to figure out if you start at the smaller servers sizes, <edit> 1) CHOOSE THE "Partially paid upfront - 1year" in the pink box dropdown to select the service/pricing, 2) then set the server XRP_PER_MONTH (row16) value to 10 per month, 3) set xrp at 1 usd( row 15) ( just to test), 4) then start by looking at row 96 (c5d.xlarge server) This is an 8 GB server, so can run 16 codius contracts. This charged at 10 XRP per month give the (16*10) = 160 XRP figure in column G, the server would then earn 160USD if XRP value=1usd. Server cost is 84.68 ( column C), this is deducted from total 160-84.68 = 75.32 ( the 100% figure in column Q:96) All the above assumed 100% uilisation which gave 160 XRP. from there easy to calculate the other %percentages.. This works the same for all rows.
  10. Suggest you play with the sheet a bit more, by changing the values shown you can model different situations, assuming you can get traffic and users are happy with the 10xrp per month ( or whatever value you set), then many AWS services could be profitable. With the sheet, there is no wrong, only a set of values. Feel free to to check the formulas - use the 100% values, the lower %'s all derive from these so easy to follow the math if you select one.
  11. Server costs are deducted in the sheet. check cell g:25 for example.. it deducts the cost of the server shown in cell c:25 after calculating the number of XRP earnt by the Codius instances running at 100%. The server earns XRP in drops, by hosting - profit is calculated by multiplying this ammount by the price of xrp..
  12. You need to specify what settings you entered.... profitability changes with each setting and service type cost,
  13. Amazon AWS EC services version available here :-
  14. Following on from the Codius hosting cost model I'd created for Packet.net, i've now completed a similar exercise for Amazon AWS EC services,..zoom out to 50% on load (google bug) EDIT - V1.3 linked corrects an error with the % utlisation calculations. Thanks to steffenmanden for spotting this. Apologies to all. https://docs.google.com/spreadsheets/d/1TaMd8GXppBhuFUzeHyh0ITp-QOU74jmzHVTPjWLTpkQ/edit?usp=sharing This one is more complex as there are so many variables ( 10 services all included).. use the pink drop down box to change the contract type, change XRP price and the monthly server charge. note - i could not lock/protect this version and keep the dropdown menu working, so it is not protected, please dont change any other variables than those detailed above , also clear in the sheet. Please see the notes at bottom -eg- no allocation for system resources has been allocated, so all memory is assigned to codius. This would need to be changed for a more accurate figure. disclaimer.. i've checked this a few times, and think its correct, but please don't use this to make decisions on starting up without doing your own calculations. Bear in mind you need to have traffic on your server to hit the targets - this is not a given and needs you to be trusted and secure, marketing etc. Send a pm if you want the original excel version. cheers joe
  15. Yup.. working on adding some of the AWS sevices to the model..they have some server packages with huge memory allocations. Bit more complex, due to their miriad of options so will take a day or so to complete.. update coming soon.