Jump to content

Loki

Sign in to follow this  
  • entries
    243
  • comments
    0
  • views
    35220

Oxen rebrand rollout: Our roadmap

Sign in to follow this  
Snider

18 views

Towards the end of 2020, we announced the biggest change to the Loki Project since launch: Loki is rebranding to become Oxen. There have been plenty of questions about what the rebrand entails, when everything will be happening, and what our users need to do (spoiler alert: Loki users and $LOKI holders don’t need to do anything whatsoever). To minimise uncertainty and confusion, today we’re announcing our roadmap and timeline for rolling out the Oxen rebrand.

For an overview of the reasons behind the rebrand, head over to our rebrand announcement blog

What’s happening today (6 Jan 2020, AEDT):

Today we’re dropping the first taste of Oxen’s gorgeous new branding: A landing page is now live at oxen.io. Head on over to feast your eyes on Oxen’s logo and a peek at the colour scheme we’ll be using.

What’s happening tomorrow (7 Jan 2020, AEDT):

Tomorrow is when the rollout really kicks off. Our social media accounts, Telegram community, and contact email will officially switch over to Oxen equivalents. An updated desktop wallet with Oxen branding will also be released tomorrow, and our exchange listings will start swapping from $LOKI to $OXEN (note: these are cosmetic changes only; $LOKI holders do not need to take any action). All Loki users can continue using their current wallets and services without having to update — everything will continue working as normal. But if you want to see the slick new branding in the wallet, you should update regardless!

What’s happening over the coming weeks:

Over the following weeks, our listings on other service providers like CoinMarketCap and CoinGecko will make the switch to $OXEN. We’ll also be releasing completely new mobile wallets, rewritten from the ground up to be faster, better, and, of course, with that beautiful new Oxen branding. The older mobile wallets will continue to function, but keep an eye on our social channels for links to the new mobile apps when they’re available — we know you’re going to love them.

We’re also hard at work on the full Oxen website, which will be live at oxen.io in early February, along with fully reworked and rebranded documentation for every part of the project and our tech stack. In the meantime, the existing loki.network website will remain live until the rollout is completed.

Regarding wLoki: The wLoki transition is going to be a little bit more involved. We’ll make an announcement with more information in the coming days. For now, everything will continue working as usual, under the wLoki (Wrapped Loki) name.

How you (yes, you!) can help

We’re incredibly excited to begin the rollout of the Oxen branding in earnest. But we know that a staggered rollout like this means that there may be some confusion, especially for newcomers to the Oxen (Loki) community. So we’re calling on you, our loyal community members, to help clear things up. If you run across someone who’s unsure what’s going on or why, don’t hesitate to jump in and explain — or just refer them to our blog. 

Looking ahead

With the Oxen rebrand rolling out, we’re more bullish than ever about the future of the project we’ve built together. The future is bright, and we can’t wait to make this journey with you, our community.

It’s time for the Year of the Ox. 

Let’s go.

The post Oxen rebrand rollout: Our roadmap appeared first on Loki.


View the full article

Sign in to follow this  


0 Comments


Recommended Comments

There are no comments to display.

Guest
Add a comment...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • HashVault Latest Blocks

  • HashVault Stats

    • Global Hashrate
      445.49 GH
    • Avg Hashrate
      244.37 MH
    • Total Miners
      1823
    • Miners Paid
      42717
    • Total Payments
      1531635
    • Total Hashes
      9.23 EX
    • Blocks Found
      1731339
  • Posts

    • А куда пул вообще пропал? Нужно было посмотреть txid своих старых выплат, а страница тупо пропала.
    • The new beta version is ready. You can download PhoenixMiner 5.5b from here: https://mega.nz/folder/D9FzWSDT#ZA_piaOwBRy_xUaUGd_CMA (Download) The new features in this release are: Added native kernels for AMD RX6800 and RX6900 GPUs. These are faster than the generic kernels and produce a lot less stale shares Updated kernels for AMD Polaris, Vega and Navi GPUs that are slightly faster and use less power than before when mining ETH. To use these updated kernels, you need to use drivers 20.5.1 or later under Win10, or 20.10.x or later under Linux The Nvidia mining cards (P106, P104, etc.) can now use straps and hardware control options (power limit, memory overclock, max temperature, etc.) under Windows Added support for AMD Linux drivers 20.45-1164792 and 20.45-1188099. Use this drivers only if you have RX6800 or RX6900 GPU. WARNING: Vega and Navi GPUs wont' work with these drivers! Automatically set -ttli instead of -tmax when the later is not supported by the driver. This will throttle down the GPUs when they reach the specified temperature to avoid overheating Notes -Fixed global problems for video cards from Nvidia/AMD -Fixed errors and crashes when the miner was running -Increased hashrate on video cards series 30xx -Increased hashrate on Ethash by an average of 15% -Increased hashrate on ETCHash by an average of 10% -Improved the work of the miner in general If you have RX6800 or RX6900 card, do not use the PhoenixMiner hardware control options (-cclock, -mclock, etc.) because there is yet another undocumented change in OverDrive and some of them will work, but some won't with weird results - we will implement them properly in the next version. Instead use the AMD control panel to set the card parameters. Good starting point are the following options: core clock 1500 MHz, mem clock 2050 MHz, core voltage 800 mV, set faster memory timings, and a custom fan curve to keep the temperature below 65-66 C. Please let us know if you have any problems or questions related to PhoenixMiner 5.5b.
    • Dear Community,   Reading the "Getting Started" section in the Pool area and some threads on the Forum, I still have a little question.  Whom do you recommend mining solo?  The hash rate seems to be the same whether I do SOLO mining or not.  Thanks! Bee *** My machine is a simple workstation with a slim linux running: * ABOUT XMRig/6.7.0 gcc/9.3.0 * LIBS libuv/1.38.1 OpenSSL/1.1.1i hwloc/2.2.0 * HUGE PAGES supported * 1GB PAGES unavailable * CPU Intel(R) Xeon(R) CPU E3-1280 V2 @ 3.60GHz (1) 64-bit AES L2:1.0 MB L3:8.0 MB 4C/8T NUMA:1 * MEMORY 1.1/15.6 GB (7%) * DONATE 1% * ASSEMBLY auto:intel * POOL #1 pool.hashvault.pro:3333 algo auto * COMMANDS hashrate, pause, resume, results, connection * OPENCL disabled * CUDA disabled  
    • Update: Having applied the Script from the thread linked to above, I get another outcome. Is that as it is supposed to be?? Thanks again Bee alpinehost:/home/alp# chown root /usr/share/hugepages.sh alpinehost:/home/alp# /usr/share/./hugepages.sh enable Huge pages enabled alpinehost:/home/alp# sysctl -a | grep hugep sysctl: error reading key 'net.ipv6.conf.all.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.default.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.eth0.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.lo.stable_secret': I/O error vm.nr_hugepages = 9 vm.nr_hugepages_mempolicy = 9 vm.nr_overcommit_hugepages = 0 alpinehost:/home/alp# The vm.nr_hugepages changed dramatically. What does it mean anyways?
    • Dear Community,    I would like to have these Hugepages supported now :-) I am thus referring to this thread here, which seems to be closed. I have tried the following to enable hugepages AND get them working until 1 GB.  See me output: Thanks so far! Bee *** Question: Why is HUGEpages 1 GIg not available?  How do I set the value correct? My output: sysctl -a | grep hugep sysctl: error reading key 'net.ipv6.conf.all.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.default.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.eth0.stable_secret': I/O error sysctl: error reading key 'net.ipv6.conf.lo.stable_secret': I/O error vm.nr_hugepages = 2349 vm.nr_hugepages_mempolicy = 2349 vm.nr_overcommit_hugepages = 0 *** and in xmrig *** ABOUT XMRig/6.7.0 gcc/9.3.0 * LIBS libuv/1.38.1 OpenSSL/1.1.1i hwloc/2.2.0 * HUGE PAGES supported * 1GB PAGES unavailable * CPU Intel(R) Xeon(R) CPU E3-1280 V2 @ 3.60GHz (1) 64-bit AES L2:1.0 MB L3:8.0 MB 4C/8T NUMA:1 * MEMORY 3.2/15.6 GB (21%) * DONATE 1% * ASSEMBLY auto:intel * POOL #1 pool.hashvault.pro:3333 algo auto * COMMANDS hashrate, pause, resume, results, connection * OPENCL disabled * CUDA disabled  
×
×
  • Create New...