So my setup is a modem and router combo given out by my isp and a tenda router connected to it, and i recently wanted to host a minecraft server, but i am a bit confused about some details. So if i recall correctly, there are 3 ways to setup the router (pppoe, dynamic IP(DHCP), or static), and its choosen by your isp. for my system, its using dynamic IP for the router, and due to how setting up the server requires port forwarding, do the ips change ( the internal ips?) i am a bit confused and could you set a ip reserve thing?
The main feature of Phorklift is using Lua as configuration. It's very clear in most cases. While it can be powerful if need. It can even create/update/delete the configuration dynamiclly, may be used for e.g. micro-service.
The project's page describes this in details and gives some configuration fragments. There are also some more complete configuration examples.
I think this is suitable for devops.
I am learning how to Host Sia Coin and I am wondering if I can get some advice on the following. In terms of hardware, I have 7 sata ports on my rig that I can use for hard drive space. Would it be most beneficial to fill these with 18 TB drives for a total of 126 TB of space for hosting or is there a hosted storage limit per cpu? I thought I saw somewhere that the host software is limited to 20 TB of storage but I may be wrong. Is there a best configuration guide for building SIA host computers? Is there a limit to the Hard Drive Space SIA will use on the host computer? If I have multiple drives of various sizes will the SIA host identify and utilize multiple drives at once or will I need to combine them to make them one drive folder for the host to point to?
https://www.toyotanation.com/threads/rear-backup-camera-guide-lines.1683281/post-14286306
Followed these steps and it worked for me! Can't believe I've been driving for 5+ months without them. After reading through several forums, it appears that a lot of dealerships have no idea that it needs to be done after delivery as part of preparation for sale.
I'm starting my build in the Lian Li PC-O11 Dynamic and I'm not sure what the best fan set up is.
I have the Corsair H150i and an additional 6 120mm fans.
Any advice would be appreciated.
I am aware that there are some linux distributions that implement BGP...
Are there any other routing protocols that have been implemented by OSs?
My question is with respect to the growing trend of layer-3 routed switching domains.
Google's fundamental switching design is layer 3 route all switching links to create giant scalable switching links; How does this factor down into the host and/or hypervisor?
Can you (for example) have this:
PC1 PC3
/ \ / \
/ \ / \
RTR1-----RTR2------RTR3-----RTR4
\ / \ /
\ / \ /
PC2 PC4
PC[1,2,3,4] each have 2 physical network adapters and 1 virtual network adapter. RTR[1,2,3,4] are regular routers.
Can this work?
The reason why I am intregued by this design, is the idea of datacenter transitory properties for virtual machines.
You could, for example, have a VM running on PC1. That VM would have 2 virtual network adapters with multiple IP addresses.
VM1, Ethernet: 1.1.1.2, 2.2.1.2, 3.3.1.2, 4.4.1.2
VM1, Ethernet 2: 1.1.2.2, 2.2.2.2, 3.3.2.2, 4.4.2.2
RTR1, Eth1: 1.1.1.1
RTR1, Eth2: 1.1.2.1
RTR2, Eth1: 2.2.1.1
RTR2, Eth2: 2.2.2.1
RTR3, Eth1: 3.3.1.1
RTR3, Eth2: 3.3.2.1
RTR4, Eth1: 4.4.1.1
RTR4, Eth2: 4.4.2.1
Then, you could configure multiple peering arrangements:
VM1, Ethernet: Peer with: [1.1.1.1, 2.2.1.1, 3.3.1.1, 4.4.1.1]
VM1, Ethernet 2: Peer with: [1.1.2.1, 2.2.2.1, 3.3.2.1, 4.4.2.1]
VM1 would then have a loopback address of 5.5.5.5, which is what all services would bind to.
In short, all the routers and all the VMs would be configured to connect to eachother, but it would only be plugged into one location at a time, so only 1 set of BGP peerings would occur, so there would only be 2 routes from anywhere in the network to 5.5.5.5 and only 1 of those would be active.
Has anyone tried setting something like this up? Is there an easier way to do this?
I want to be able to have ~ 300 VMs, each with their own subnet (a /32). Then, each of those VMs would have 2 active BGP (or any other routing protocol) sessions with [which ever 2 routers are connected to the hypervisor that VM is running on].
Then, by virtue of the VMs being able to form BGP relationships only with the routers adjascent to them (at layer 2), the routing tables on the network will take care of moving that /32 subnet around throughout
... keep reading on reddit ➡A new project called Retro DeFi - RCUBE
The current mCap is $2,056,815.
The project looks really cool as well with retro 80s synthwave branding and UI.
----------------------------------
⭐ About RCUBE
RCUBE runs on a dynamic supply protocol that has automatic burns correlating with the number of transactions being made in the network—creating a decreasing supply of RCUBE. This, as a result, drives up the value of RCUBE as the supply decreases and coins become more scarce.
The total supply is low. It started at 25,000,000.
With current activity, the supply has decreased to 22,884,485.
Probably it decreased a bit more while I wrote this post. You can check it on BSCscan for yourself:
https://bscscan.com/token/0xa6e53f07bD410df069e20Ced725bdC9135146Fe9
As you can see there, RCUBE is a BEP20 token running on the Binance Smart Chain.
----------------------------------
⭐ RCUBE tokenomics
On every transaction that is made on the network, a burn (fee) is applied. This fee ranges between 2.5% - 6%. Starting at 2.5%, the fee increase by 1% for every 500,000 RCUBE transacted. This is called the “Deflationary” phase.
At the same time, to reward holders of RCUBE, a redistribution is made. This is also based on the number of RCUBE transacted. When the deflationary phase is over after 2,500,000 RCUBE have been transacted, 25% of the total amount of RCUBE burnt during the cycle is redistributed. This is called the “Rebase” phase.
After that, the phases repeat. Over and over, until the max supply has reached 8,000,000.
At that point, the max supply reaching 8,000,000. Holders would have been rewarded handsomely through redistribution along the way and with a value per token increasing as the supply decrease.
The redistribution is friction-free. All you need to do is hold RCUBE in your wallet. No LP or Farming is involved. Basically, your holdings are auto-compounding with no lock-up or unstake period.
Before moving on to the roadmap, features, and utility. Here is a breakdown of the RCUBE supply:
Pre-sale 50% = 12,500,000
Liquidity 40% = 10,000,000
Marketing 5% = 1,250,000
Retro DeFi team 5% = 1,250,000
Yesterday, the Retro DeFi team announced that they locked a majority of the 5% along with a part of the marketing budget. The contract is locked for three months. During which time, none of these tokens can be sold. Once the contract expires, they will evaluate whether t
... keep reading on reddit ➡I'm about a month away from having all the components to build a complete PC. The case I went with is the Lian Li PC-O11 Dynamic (like everyone else apparently). However I've been thinking about a 9 fan config that, in theory, would give decent temps as well as great aesthetics.
3 fans at the bottom - Intake
360mm AIO top intake (Push)
3 fans at the side - Exhaust
Any thoughts about why this would/wouldn't work? And please don't give me the whole "heat rises" speech. While true, it's not really that simple and relevant. Fans powerful enough can neglect that effect.
🖌 Design Ethos
We have designed many parameters in Alpaca Finance to be configurable. While the initial configurations are set by the core developer team, we have every intention to let the Governance community decide on what needs to be changed which will happen through voting.
⏳ Timelock
Timelock is a contract for delaying changes to the protocol. This contract is an owner of all the major contracts in Alpaca Finance. Hence, every change needs to execute through this contract, which makes it function as a security moat.
In essence, every order from the admin(the group of core developers) has to pass through this contract and is delayed for 24 hours before taking effect. To be specific, the execution command for the order goes to the queue, waiting to be executed when the 24h delay is passed. This is a security feature that enables the community to see any upcoming updates and prepare in advance for them. If anything looks suspicious, they can pull their funds from the protocol before the update takes effect.
Below are the contracts owned by Timelock
- All Vault Contracts
- FairLaunch Contract
- All Worker Contracts
- All PriceOracle Contracts
- All WorkerConfig Contracts
⚙ Adjustable Parameters
This section lists all adjustable parameters and functions in Alpaca Finance
FairLaunch Contract
-
addPool(_allocatedPoint, _stakeToken, _withUpdate)
- _allocatedPoint = How many points assign to this pool. This will affect the ALPACAs distribution per block.
- _stakeToken = The address of a required staking token.
- _withUpdate = A flag for updatePool calculation
-
setPool(_pid, _allocatedPoint, _withUpdate)
- _pid = Pool ID that you wish to adjust the point
- _allocatedPoint = New points to be assign to this pool. This will affect the ALPACAs distribution per block.
- _withUpdate = A flag for updatePool calculation
-
setBonus(_bonusMultiplier, _bonusEndBlock, _bonusLockUpBps)
- _bonusMultiplier = Multiplier that will be applied during the bonus period
- _bonusEndBlock = The block number that bonus will be ended
- _bonusLockUpBps = % of bonus that is earned in the bonus period to be locked
Vault Contract
-
updateConfig(_newConfig)
- _newConfig = A new contract that is implemented IVaultConfig interface
-
setFairLaunchPoolId(_pid)
- _pid = Pool ID on Fair Contract that the staking token is debtToken owned by Vault
-
withdrawReserve(_to, _amount)
- _to = The addre
Hello everyone!
I recently finished putting together a rig in the O11 Dynamic with a 5900X and 3090 K|NGP|N, but couldn't help but wonder what the best configuration would be for the radiators and fans.
Link for pictures and more details
As of now, it is configured as follows:
- Bottom 3 Arctic P12 fans intaking air
- Side-mounted K|NGP|N radiator with 3 Arctic P12s exhausting (in push)
- Top-mounted EKWB 360mm AIO with 3 Arctic P12s exhausting (in push)
With the current setup, I am creating a negative pressure environment (which I am fine with cleaning every so often, PC is on my desk next to me so its pretty simple) and making sure the 500W+ air from the GPU doesn't make its way to the rest of the components.
Everything that I've read so far only accounts for 1 radiator for CPU thermals with an air-cooled GPU, so this is a bit different.
However, I do feel like the rest of the components (VRAM, DIMMs, VRMs, CPU AIO) may be starved for fresh air in this configuration, but in reality, I'm not entirely sure how much of a difference it would make. Further, I'm unsure if I need to run the bottom-mounted fans harder to provide fresh air for the 6 exhaust fans, or if that even matters to begin with.
As an aside, I just received my 3 Scythe Wonder Snail 120mm fans, and I'm guessing the best place for them would be on the KINGPIN radiator for maximum performance, but any other advice would be appreciated.
Thanks in advance!
Hello
Didn't find anything regarding this topic here on reddit. I operate a small vSphere/vSAN cluster with latest releases (7.0U2a/b) and needed to change NTP servers due to network changes.
Now vSAN Skyline Health shows this warning constantly:
https://preview.redd.it/t5mncplwzn371.png?width=1699&format=png&auto=webp&s=7a04abbbff5a6adf811856c6c88a2e1573ac60ac
VMware KB recommends to "Configure NTP on vSAN Host to match with other vSAN Hosts" (https://kb.vmware.com/s/article/58896) which doesn't help.
Others report same behaviour, see blog entry and VMware forums. Recreating the cluster from scratch isn't an option for me...
Probably experts here know some solution to change the settings entered in Cluster Quickstart after having completed cluster setup to get rid off this annoying warning?
Many thanks!
Hello everyone,
I just released Part 1 of my two-part lesson on Routers:
https://www.youtube.com/watch?v=AzXys5kxpAM
This video discusses Routers and everything Routers do to facilitate communication between networks.
We first describe that Routers and Hosts are very similar, then provide a formal definition of a Router and Host (and Nodes). Then we discuss the Routing Table and show you how a Router uses it to route packets. Finally, we illustrate the three methods a Router populates its Routing Table: Directly Connected routes, Static Routes, Dynamic Routes.
The specific time stamps to each of these sections are below:
- 00:00 - Start
- 00:20 - Pre-requisites (Networks, Routing, OSI Model, L2 & L3, Everything Hosts do, ARP)
- 02:09 - Routers need an IP Address and MAC address (just like hosts)
- 03:19 - Formal Definitions: Routers and Hosts (and Nodes)
- 05:02 - Routers need an IP/MAC for EACH Network
- 05:45 - Routing Table
- 07:22 - Directly Connected Routes
- 09:27 - Using the Routing Table to route Packets
- 10:39 - Static Routes
- 11:50 - Forward and Return path
- 13:04 - Dynamic Routes
- 14:35 - Dynamic Routing Protocols
- 15:31 - Summary & Key Points
- 16:24 - Network Fundamentals - Full Course - Details
A lot of effort was put into this video, and I feel confident in saying you will be hard pressed to find these ideas communicated in a more lucid way.
Either way, feedback is always appreciated (positive or negative). So please let me know what you think.
PS: If you're interested in the full series this video stems from, [click here
... keep reading on reddit ➡Hello there! I am interested in using a Signal proxy using this official documentation:
https://github.com/signalapp/Signal-TLS-Proxy
However, my server already has Nginx set up, so is there a way to host this on another port (other than 80 or 443) [maybe by editing the docker compose yml file) to then integrate that into my already running nginx setup?
I would like to run this on a Raspberry Pi.
Any ideas on how to accomplish this/are there already forks that allow this? I don't want to run an entirely new instance of Nginx, or am I misunderstanding something?
Any help is appreciated.
Hi all:
TL:DR I'm a paramedic that manages a huge set of documents and what I'm using right now isn't working. HALP.
Tons of info included below because I typed it all out for engineer brother's assistance and thought it might be helpful in answering questions.
###
Accidental medical writer here: please forgive my incorrect terminology at any point as I fell into this job because I have a good vocabulary and I like styling documents. I'm hoping that industry professionals can point me in the right direction regarding software/platform/CMS.
I am responsible for a "protocol set" of documents (~300-ish?) that is often changed, most often minor changes (e.g. Morphine dosage for sedation is now 0.25 mg/kg instead of 0.2 mg/kg) driven by medical research, our medical director's request, supply availability (thank you COVID), etc. Right now when changes are made it's a horribly gluggy process...safe to say it includes Microsoft Word, pushing to PDF, and reassembling a really huge document that's then pushed out to a lot of different places. Blech.
I earned the right to be responsible for this task because I'm really good at copyediting; 4 years later I'm a paramedic trying to figure out if MadCap Flare or FrameMaker (or something else) is the best software to recommend to my boss. He really likes Adobe, but I'm the main writer/editor. Is FrameMaker really the best option? He's touting its interface with Adobe Experience Manager, saying that it would be useful to us.
I on the other hand just figured out WordPress. Woo. /s
Info:
End-users are street paramedics that use these documents as a reference for off-line medical control; e.g. what the doctor in charge says they are allowed to do with certain types of patients. They most often utilize it on phones/tablets, so search ability is critical and the need for pinch/zoom to read PDFs is difficult because of gloves.
- ~300 documents (individual "protocols") organized into relevant folders (could change, maybe tags?)
- *Ex: Clinical Policies, Operational Policies, Adult Medical, Pediatric Medical, Trauma, Procedures, Appendices
- Entire protocol set is presently in Word, being pushed to PDF when needed *groan*
- Organization has Adobe Acrobat and Office365.
- Very few people work on these documents, most are view-only.
Needs:
- Need ability to push to PDF or something printable at any point (state law)
- Version review and way to document changes made
- Search is critical
- Sunset
I'm considering to make a Lian Li O11 Mini build myself and therefore I'm figuring out how to place my fans.
Which one might result in better GPU and CPU temperatures?
-
- 240mm AIO side exhaust, 1x rear exhaust, 3x bottom intake Unifans
-
- 240mm AIO side exhaust, 1x rear exhaust, 3x top exhaust Unifans
(or even)
-
- 240mm AIO side exhaust, 1x rear INTAKE, 3x bottom intake/3x top exhaust
As you can tell I'm on a budget and therefore only able to mount 3x fans in the top or bottom.
I hope you can help me to decide which config I should pick! THX
We are troubleshooting some performance differences between ESX hosts and I am looking for a report to compare them. I see where I can 'Export System Logs' but it outputs a lot of files that seem to be for VMWare diagnostics and not really a human-readable report.
Any suggestions?
Two new AIPs (AirSwap Improvement Proposals) are in the works right now:
AIP 19: Time-Weighted Voting Points
The proposal is to create a loyalty point system that rewards active participation in governance and long-term staking of AST.
AIP 20: Protocol Configurations Weighted Voting
Goal is to make the protocol configuration propositions to be voted and accepted in a more fair way.
Join the Discord or the Forum to discuss the proposals with other community members or start drafting your own AIP by visiting the #aip-help channel on Discord. For more information on creating your own proposal take a look at the guide on the forum.
Hi, been looking at several web pages on the topic and i just can't seem to find what I'm looking for.
I have a list of
<button>Wifi_1</button>
<button>Wifi_2</button> ...
On this try-me page from w3schools we can see that it's got almost everything I want. It's got a text field form and a drop down selector. https://www.w3schools.com/tags/tryit.asp?filename=tryhtml5_select_form
I originally had quite a lengthy writeup but honestly, the question I have now is, what's the button equivalent of a select list?
I've looked into this topic pretty deep already and as far as I'm aware, I don't think It can be done. I can't use radio buttons since they can't be styled to look like buttons. I can't use javascript to transform buttons into radio-like buttons.
A new project called Retro DeFi - RCUBE
The current mCap is $1,556,815.
The project looks really cool as well with retro 80s synthwave branding and UI.
About RCUBE
RCUBE runs on a dynamic supply protocol that has automatic burns correlating with the number of transactions being made in the network—creating a decreasing supply of RCUBE. This, as a result, drives up the value of RCUBE as the supply decreases and coins become more scarce.
The total supply is low. It started at 25,000,000.
With current activity, the supply has decreased to 23,293,435.
Probably it decreased a bit more while I wrote this post. You can check it on BSCscan for yourself:
https://bscscan.com/token/0xa6e53f07bD410df069e20Ced725bdC9135146Fe9
As you can see there, RCUBE is a BEP20 token running on the Binance Smart Chain.
RCUBE tokenomics
On every transaction that is made on the network, a burn (fee) is applied. This fee ranges between 2.5% - 6%. Starting at 2.5%, the fee increase by 1% for every 500,000 RCUBE transacted. This is called the “Deflationary” phase.
At the same time, to reward holders of RCUBE, a redistribution is made. This is also based on the number of RCUBE transacted. When the deflationary phase is over after 2,500,000 RCUBE have been transacted, 25% of the total amount of RCUBE burnt during the cycle is redistributed. This is called the “Rebase” phase.
After that, the phases repeat. Over and over, until the max supply has reached 8,000,000.
At that point, the max supply reaching 8,000,000. Holders would have been rewarded handsomely through redistribution along the way and with a value per token increasing as the supply decrease.
The redistribution is friction-free. All you need to do is hold RCUBE in your wallet. No LP or Farming is involved. Basically, your holdings are auto-compounding with no lock-up or unstake period.
Before moving on to the roadmap, features and utility. Here is a breakdown of the RCUBE supply:
- Pre-sale 50% = 12,500,000
- Liquidity 40% = 10,000,000
- Marketing 5% = 1,250,000
- Retro DeFi team 5% = 1,250,000
Yesterday, the Retro DeFi team announced that they locked a majority of the 5% along with a part of the marketing budget. The contract is locked for three months. During which time, none of these tokens can be sold. Once the contract expires, they will evaluate whether they will lock it up again, where the amount may vary depending on budg
... keep reading on reddit ➡A new project called Retro DeFi - RCUBE
The current mCap is $1,556,815.
The project looks really cool as well with retro 80s synthwave branding and UI.
About RCUBE
RCUBE runs on a dynamic supply protocol that has automatic burns correlating with the number of transactions being made in the network—creating a decreasing supply of RCUBE. This, as a result, drives up the value of RCUBE as the supply decreases and coins become more scarce.
The total supply is low. It started at 25,000,000.
With current activity, the supply has decreased to 23,293,435.
Probably it decreased a bit more while I wrote this post. You can check it on BSCscan for yourself:
https://bscscan.com/token/0xa6e53f07bD410df069e20Ced725bdC9135146Fe9
As you can see there, RCUBE is a BEP20 token running on the Binance Smart Chain.
RCUBE tokenomics
On every transaction that is made on the network, a burn (fee) is applied. This fee ranges between 2.5% - 6%. Starting at 2.5%, the fee increase by 1% for every 500,000 RCUBE transacted. This is called the “Deflationary” phase.
At the same time, to reward holders of RCUBE, a redistribution is made. This is also based on the number of RCUBE transacted. When the deflationary phase is over after 2,500,000 RCUBE have been transacted, 25% of the total amount of RCUBE burnt during the cycle is redistributed. This is called the “Rebase” phase.
After that, the phases repeat. Over and over, until the max supply has reached 8,000,000.
At that point, the max supply reaching 8,000,000. Holders would have been rewarded handsomely through redistribution along the way and with a value per token increasing as the supply decrease.
The redistribution is friction-free. All you need to do is hold RCUBE in your wallet. No LP or Farming is involved. Basically, your holdings are auto-compounding with no lock-up or unstake period.
Before moving on to the roadmap, features and utility. Here is a breakdown of the RCUBE supply:
- Pre-sale 50% = 12,500,000
- Liquidity 40% = 10,000,000
- Marketing 5% = 1,250,000
- Retro DeFi team 5% = 1,250,000
Yesterday, the Retro DeFi team announced that they locked a majority of the 5% along with a part of the marketing budget. The contract is locked for three months. During which time, none of these tokens can be sold. Once the contract expires, they will evaluate whether they will lock it up again, where the amount may vary depending on budg
... keep reading on reddit ➡A new project called Retro DeFi - RCUBE
The current mCap is $1,556,815.
The project looks really cool as well with retro 80s synthwave branding and UI.
About RCUBE
RCUBE runs on a dynamic supply protocol that has automatic burns correlating with the number of transactions being made in the network—creating a decreasing supply of RCUBE. This, as a result, drives up the value of RCUBE as the supply decreases and coins become more scarce.
The total supply is low. It started at 25,000,000.
With current activity, the supply has decreased to 23,293,435.
Probably it decreased a bit more while I wrote this post. You can check it on BSCscan for yourself:
https://bscscan.com/token/0xa6e53f07bD410df069e20Ced725bdC9135146Fe9
As you can see there, RCUBE is a BEP20 token running on the Binance Smart Chain.
RCUBE tokenomics
On every transaction that is made on the network, a burn (fee) is applied. This fee ranges between 2.5% - 6%. Starting at 2.5%, the fee increase by 1% for every 500,000 RCUBE transacted. This is called the “Deflationary” phase.
At the same time, to reward holders of RCUBE, a redistribution is made. This is also based on the number of RCUBE transacted. When the deflationary phase is over after 2,500,000 RCUBE have been transacted, 25% of the total amount of RCUBE burnt during the cycle is redistributed. This is called the “Rebase” phase.
After that, the phases repeat. Over and over, until the max supply has reached 8,000,000.
At that point, the max supply reaching 8,000,000. Holders would have been rewarded handsomely through redistribution along the way and with a value per token increasing as the supply decrease.
The redistribution is friction-free. All you need to do is hold RCUBE in your wallet. No LP or Farming is involved. Basically, your holdings are auto-compounding with no lock-up or unstake period.
Before moving on to the roadmap, features and utility. Here is a breakdown of the RCUBE supply:
- Pre-sale 50% = 12,500,000
- Liquidity 40% = 10,000,000
- Marketing 5% = 1,250,000
- Retro DeFi team 5% = 1,250,000
Yesterday, the Retro DeFi team announced that they locked a majority of the 5% along with a part of the marketing budget. The contract is locked for three months. During which time, none of these tokens can be sold. Once the contract expires, they will evaluate whether they will lock it up again, where the amount may vary depending on budg
... keep reading on reddit ➡A new project called Retro DeFi - RCUBE
The current mCap is $1,556,815.
The project looks really cool as well with retro 80s synthwave branding and UI.
About RCUBE
RCUBE runs on a dynamic supply protocol that has automatic burns correlating with the number of transactions being made in the network—creating a decreasing supply of RCUBE. This, as a result, drives up the value of RCUBE as the supply decreases and coins become more scarce.
The total supply is low. It started at 25,000,000.
With current activity, the supply has decreased to 23,293,435.
Probably it decreased a bit more while I wrote this post. You can check it on BSCscan for yourself:
https://bscscan.com/token/0xa6e53f07bD410df069e20Ced725bdC9135146Fe9
As you can see there, RCUBE is a BEP20 token running on the Binance Smart Chain.
RCUBE tokenomics
On every transaction that is made on the network, a burn (fee) is applied. This fee ranges between 2.5% - 6%. Starting at 2.5%, the fee increase by 1% for every 500,000 RCUBE transacted. This is called the “Deflationary” phase.
At the same time, to reward holders of RCUBE, a redistribution is made. This is also based on the number of RCUBE transacted. When the deflationary phase is over after 2,500,000 RCUBE have been transacted, 25% of the total amount of RCUBE burnt during the cycle is redistributed. This is called the “Rebase” phase.
After that, the phases repeat. Over and over, until the max supply has reached 8,000,000.
At that point, the max supply reaching 8,000,000. Holders would have been rewarded handsomely through redistribution along the way and with a value per token increasing as the supply decrease.
The redistribution is friction-free. All you need to do is hold RCUBE in your wallet. No LP or Farming is involved. Basically, your holdings are auto-compounding with no lock-up or unstake period.
Before moving on to the roadmap, features and utility. Here is a breakdown of the RCUBE supply:
- Pre-sale 50% = 12,500,000
- Liquidity 40% = 10,000,000
- Marketing 5% = 1,250,000
- Retro DeFi team 5% = 1,250,000
Yesterday, the Retro DeFi team announced that they locked a majority of the 5% along with a part of the marketing budget. The contract is locked for three months. During which time, none of these tokens can be sold. Once the contract expires, they will evaluate whether they will lock it up again, where the amount may vary depending on budg
... keep reading on reddit ➡A new project called Retro DeFi - RCUBE
The current mCap is $1,556,815.
The project looks really cool as well with retro 80s synthwave branding and UI.
About RCUBE
RCUBE runs on a dynamic supply protocol that has automatic burns correlating with the number of transactions being made in the network—creating a decreasing supply of RCUBE. This, as a result, drives up the value of RCUBE as the supply decreases and coins become more scarce.
The total supply is low. It started at 25,000,000.
With current activity, the supply has decreased to 23,293,435.
Probably it decreased a bit more while I wrote this post. You can check it on BSCscan for yourself:
https://bscscan.com/token/0xa6e53f07bD410df069e20Ced725bdC9135146Fe9
As you can see there, RCUBE is a BEP20 token running on the Binance Smart Chain.
RCUBE tokenomics
On every transaction that is made on the network, a burn (fee) is applied. This fee ranges between 2.5% - 6%. Starting at 2.5%, the fee increase by 1% for every 500,000 RCUBE transacted. This is called the “Deflationary” phase.
At the same time, to reward holders of RCUBE, a redistribution is made. This is also based on the number of RCUBE transacted. When the deflationary phase is over after 2,500,000 RCUBE have been transacted, 25% of the total amount of RCUBE burnt during the cycle is redistributed. This is called the “Rebase” phase.
After that, the phases repeat. Over and over, until the max supply has reached 8,000,000.
At that point, the max supply reaching 8,000,000. Holders would have been rewarded handsomely through redistribution along the way and with a value per token increasing as the supply decrease.
The redistribution is friction-free. All you need to do is hold RCUBE in your wallet. No LP or Farming is involved. Basically, your holdings are auto-compounding with no lock-up or unstake period.
Before moving on to the roadmap, features and utility. Here is a breakdown of the RCUBE supply:
- Pre-sale 50% = 12,500,000
- Liquidity 40% = 10,000,000
- Marketing 5% = 1,250,000
- Retro DeFi team 5% = 1,250,000
Yesterday, the Retro DeFi team announced that they locked a majority of the 5% along with a part of the marketing budget. The contract is locked for three months. During which time, none of these tokens can be sold. Once the contract expires, they will evaluate whether they will lock it up again, where the amount may vary depending on budg
... keep reading on reddit ➡A new project called Retro DeFi - RCUBE
The current mCap is $1,556,815.
The project looks really cool as well with retro 80s synthwave branding and UI.
About RCUBE
RCUBE runs on a dynamic supply protocol that has automatic burns correlating with the number of transactions being made in the network—creating a decreasing supply of RCUBE. This, as a result, drives up the value of RCUBE as the supply decreases and coins become more scarce.
The total supply is low. It started at 25,000,000.
With current activity, the supply has decreased to 23,293,435.
Probably it decreased a bit more while I wrote this post. You can check it on BSCscan for yourself:
https://bscscan.com/token/0xa6e53f07bD410df069e20Ced725bdC9135146Fe9
As you can see there, RCUBE is a BEP20 token running on the Binance Smart Chain.
RCUBE tokenomics
On every transaction that is made on the network, a burn (fee) is applied. This fee ranges between 2.5% - 6%. Starting at 2.5%, the fee increase by 1% for every 500,000 RCUBE transacted. This is called the “Deflationary” phase.
At the same time, to reward holders of RCUBE, a redistribution is made. This is also based on the number of RCUBE transacted. When the deflationary phase is over after 2,500,000 RCUBE have been transacted, 25% of the total amount of RCUBE burnt during the cycle is redistributed. This is called the “Rebase” phase.
After that, the phases repeat. Over and over, until the max supply has reached 8,000,000.
At that point, the max supply reaching 8,000,000. Holders would have been rewarded handsomely through redistribution along the way and with a value per token increasing as the supply decrease.
The redistribution is friction-free. All you need to do is hold RCUBE in your wallet. No LP or Farming is involved. Basically, your holdings are auto-compounding with no lock-up or unstake period.
Before moving on to the roadmap, features and utility. Here is a breakdown of the RCUBE supply:
- Pre-sale 50% = 12,500,000
- Liquidity 40% = 10,000,000
- Marketing 5% = 1,250,000
- Retro DeFi team 5% = 1,250,000
Yesterday, the Retro DeFi team announced that they locked a majority of the 5% along with a part of the marketing budget. The contract is locked for three months. During which time, none of these tokens can be sold. Once the contract expires, they will evaluate whether they will lock it up again, where the amount may vary depending on budg
... keep reading on reddit ➡A new project called Retro DeFi - RCUBE
The current mCap is $1,556,815.
The project looks really cool as well with retro 80s synthwave branding and UI.
About RCUBE
RCUBE runs on a dynamic supply protocol that has automatic burns correlating with the number of transactions being made in the network—creating a decreasing supply of RCUBE. This, as a result, drives up the value of RCUBE as the supply decreases and coins become more scarce.
The total supply is low. It started at 25,000,000.
With current activity, the supply has decreased to 23,293,435.
Probably it decreased a bit more while I wrote this post. You can check it on BSCscan for yourself:
https://bscscan.com/token/0xa6e53f07bD410df069e20Ced725bdC9135146Fe9
As you can see there, RCUBE is a BEP20 token running on the Binance Smart Chain.
RCUBE tokenomics
On every transaction that is made on the network, a burn (fee) is applied. This fee ranges between 2.5% - 6%. Starting at 2.5%, the fee increase by 1% for every 500,000 RCUBE transacted. This is called the “Deflationary” phase.
At the same time, to reward holders of RCUBE, a redistribution is made. This is also based on the number of RCUBE transacted. When the deflationary phase is over after 2,500,000 RCUBE have been transacted, 25% of the total amount of RCUBE burnt during the cycle is redistributed. This is called the “Rebase” phase.
After that, the phases repeat. Over and over, until the max supply has reached 8,000,000.
At that point, the max supply reaching 8,000,000. Holders would have been rewarded handsomely through redistribution along the way and with a value per token increasing as the supply decrease.
The redistribution is friction-free. All you need to do is hold RCUBE in your wallet. No LP or Farming is involved. Basically, your holdings are auto-compounding with no lock-up or unstake period.
Before moving on to the roadmap, features and utility. Here is a breakdown of the RCUBE supply:
- Pre-sale 50% = 12,500,000
- Liquidity 40% = 10,000,000
- Marketing 5% = 1,250,000
- Retro DeFi team 5% = 1,250,000
Yesterday, the Retro DeFi team announced that they locked a majority of the 5% along with a part of the marketing budget. The contract is locked for three months. During which time, none of these tokens can be sold. Once the contract expires, they will evaluate whether they will lock it up again, where the amount may vary depending on budg
... keep reading on reddit ➡