We intend to make this claim process as fair and transparent as possible and it can therefore be audited on the blockchain.
To maintain a healthy staking network we recommend people participate in the off-exchange claim process for the bulk of their holdings.
You may want to consolidate some of your holdings to a smaller number of JBS addresses leading up to the swap.
Thank you for your participation!
Jumbucks is a Fair Launch cryptocurrency which launched in September 2014 without an IPO and with zero premine. Jumbucks currently runs as 100% Proof of Stake, and is currently traded on Bittrex and Cryptopia. Find out more information at GetJumbucks.com. Jumbucks will be swapping to a new chain, Ubiq (UBQ), which will be an Ethereum fork with new features!
Sign up to Jumbucks Slack to be a part of a growing community of over 640 crypto enthusiasts and Jumbucks fans!
Follow @getjumbucks on Twitter for all the latest news and announcements!
NavCore Project Progress, Nav Community & Marketing Update
has been a lot of solid progress made this week as the new team members
start contributing to the main projects they will be working on. We will
keep you updated on each project’s progress as milestones are achieved.
Don’t forget it’s all open source so you can follow along on the
NavCoin GitHub and even get involved!
NavCore Project Progress
week the NavCoin Core Team (NavCore) have made continued progress
across their range of current projects. NavPi Kowhai has seen a
significant increase in GitHub activity as Mike gets up and running as a
full time contributor. As well as helping Mike get started, Paul has
been busy setting up development containers so all new developers can
get up and running faster. So far he’s set up dev containers for NavCoin
Core, NavMorph and NavPi Kowhai. Paul is also working to investigate
upgrade and maintenance paths for the main repositories which have been
forked from other projects, NavCoin Core and NavPay. This will allow
them to be kept more easily updated as new versions get released on the
has been working to get Rowan started on the NavMorph project, as well
as some helpful peripheral tasks like flashing NavPi SD cards and
writing articles for the knowledge base. Rowan has started reviewing
NavMorph firstly to get an overview of where it’s at, how he can
contribute and what needs to be audited before moving forward. As well
as NavMorph, Rowan has been in talks with community moderator mntyfrsh
about strengthening and standardizing the server architecture of the
primary NavCoin services that the NavCore Team host are run on.
continues to make progress on NavCoin Core with about 5 pull requests
being completed this week. The rest of the NavCore team are busy working
with Alex to increase their understanding of the NavCoin Core code base
and support his pull requests by performing code reviews and approving
the merges. The NavCore team are also joining the wider community
efforts to test the Community Fund for any bugs or improvements that
need to be implemented. Once the community is happy it works correctly,
it will be added to the main network through the built-in majority
network consensus approval process.
can see all of this progress on a daily basis if you follow our GitHub
repositories. The progress indicators on NavCore’s project roadmap have
been updated on the website.
The NavCoin Community
NavCore team remain fully committed to furthering the development of
NavCoin, all its projects and initiatives. This should be abundantly
clear from our actions and expansions over the recent months. It’s a big
job though and we can’t do it all by ourselves. We need your help.
is a community initiative. NavCoin ran no ICO or token sale to fund its
development. The NavCore team is entirely comprised of and self-funded
by community members and individuals who believe in the NavCoin project.
NavCore team contribute to and try to guide NavCoin as best they can,
but NavCore is in essence a part of the NavCoin community and ultimately
NavCoin’s future is in the hands of the entire NavCoin community. It’s
this position which has made Bitcoin so strong, and it is what will
ensure NavCoin is too.
the spirit of being an open source project, we are working on ways to
further decentralize the stewardship of NavCoin beyond having all the
NavCore projects open source. The Community Fund will be a big help to
all of the NavCoin projects and initiatives of the wider community. So
make sure you help us test it and get it across the line!
also want to drive a higher level of community involvement in the
websites and social media accounts which NavCore manage. For obvious
reasons we can’t simply make the NavCoin twitter password public or add
every community member as an Admin to the NavCoin website, but we do
want to make sure the community is fairly represented through these
now, the best place to get in touch with the NavCore team about this is
through discord. If you’re running a NavCoin competition, let us know
and we’ll tweet about it! If you’re working on a cool NavCoin project,
let us know and we’ll add it to the project roadmap! If you want
something changed on the website, then let us know and we’ll update it!
currently investigating more transparent and democratic ways to get the
community involved in these processes, so there will be more to come on
this in future updates.
NavCore marketing team have released an update on Reddit, as a way to
give you a sense of what they are working on at the moment and what’s
A couple of take aways:
NavCore marketing team are looking for two new team members to join
them in Auckland — a UX/UI designer, and a technical content writer.
These additions will increase both the quality, and the volume of
marketing activities from the team.There
is one more article in the Valence introduction series to go, and once
that’s completed they will put their focus back onto NavCoin. The team
is in the process of finalizing their vision & strategy for NavCoin,
and are taking the time to get it right. This will be released as a
content series, and will give the community a better view on how NavCoin
fits into the crypto ecosystem, and how it will stand out.
Hey everyone! We just wanted to post an informal update on the marketing team and what’s on the cards for the near future.
Changes to the marketing team:
Expanding the team - we’re in the process of hiring some new members
to join our Auckland team. We’ve got a lot of tasks on our to-do lists,
so this will be a huge benefit and allow us to get a lot more done.
Initially, we will be adding a Graphic Designer / User Interface expert
to help create more visual content for our marketing activities, and
refine our websites/application interfaces. We’re also looking to hire a
technical content writer to contribute to our ongoing articles and
marketing content.Building better processes. It’s been a challenge trying to balance
everything we need/want to do, and the result is that our team has been
spread thin. So we’re building in team processes to ensure that our
social activity & community engagement get the attention they
Roadmap for the short term:
Valence introduction series. Our immediate focus is finishing the
Valence introduction series. We want the community to get an idea of
what it’s all about, as a lead up to the release of the technical white
paper.NAV Values/Mission/Strategy articles. This has largely been defined,
and we are now just refining this with a few of our advisors. Will be
next in line to be released after this initial series about Valence.NavCoin & Valence branding. Working with a specialist brand
designer to refresh the NavCoin branding and create the visual
designs/assets to bring Valence into the family.Website update/refresh. Updating and reorganizing the content on the
website to be more engaging and up-to-date. We’ll be starting with the
English version of the site, and then will roll it out across different
languages (this has been a very manual process in the past, so we’re
looking into ways to automate this). This will be an ongoing task over
the next 6 months.Public Relations Activities. We want to get our brand into the wider
public attention, so this is about properly crafting our stories and
reaching out to journalists/influencers.Product development. Working with the developers to refine our
products, and ensure they are user-friendly and beautifully designed.
The immediate ones we will be working on include NavPi 2.0 and NavMorph.NavCoin knowledge base. Continuing to produce content for the
knowledge base, so that it becomes an even more useful hub of
We're also working to improve:
Community engagement. As we mentioned, we’re working to improve our
processes to better manage our engagement with the community. We’re
aiming to do more projects that tap into the energy that our community
has for NavCoin, by working more closely with the moderators to help
these projects along.Social content. This will also benefit from our improved processes -
so that there is a wider range of content, and tailored posts based on
the social channel (FB/Twitter/Instagram/etc)Weekly updates. We’re keen to hear the communities feedback on our
weekly reports, so we’ll aim to put out a survey in the near future.
MaidSafe Dev Update - Marketing, SAFE Authenticator & API & More
Here are some of the main things to highlight this week:
Yesterday, we released a new video40 that explains how the SAFE Network differs from blockchain-based solutions.The poll for choosing a proposal for the Safecoin Video Animation CEP13 is closing tomorrow. Forum users who are at trust level 12 and above can vote here.The Marketing team has created a new Medium publication (https://medium.com/safenetwork34) to collect content related to the SAFE Network in a single location.All
members of the SAFE Client Libs team will soon join the Routing team
(some have already joined) to help with Routing development.
New video released
As mentioned in last week’s update about the marketing plans for H1 20185, we are keen to share with the community the broad messages that we’ll be focusing on when talking about the project.
of these messages highlights our distinct approach which differs from,
and we believe improves upon, blockchain solutions. In order to support
this message, we released a new video yesterday40.
We’d be grateful if you could all share widely please across your own
social media channels. We need this message out there to build upon the
differentiation as the year moves on.
SAFE Network Primer
also identified that we have a challenge in directing people towards
resources. Just before Christmas, we received an early present from @jpl and @polpolrene
in the form of a lengthy document called ‘The SAFE Network Primer’. The
product of a huge amount of time and effort, this is a 30-page
introduction that can be shared freely with anyone who is new to the
project and looking for a summary. It’ll also be useful to those who
perhaps have been following the project for a while but don’t have the
time to forage around the Forum as they field questions from others. We
now have a final version of this document and we’ll be pushing it out to
the community any day now. Once again, we’d ask everyone to share it as
widely as possible. Thanks again to @jpl and @polpolrene for all their hard work.
Community Engagement Program update
seen a good deal of interaction in our CEP to create a Safecoin video.
We received four fantastic submissions, all quite different and the poll
will be closing tomorrow (Friday 19th). The team has tried to stay out
of the conversation on the Forum as far as possible in order to ensure
that the community isn’t influenced in any way and we’d encourage you to
vote if you haven’t already. We’re looking at a few changes for the
next CEP, including the funding mechanism given the backlog on the
network so we’ll keep you all updated.
New Medium publication
the years, there has been a variety of written commentary spread out
between blogs (individuals and the company) and on other websites. As an
experiment, we’ve now pulled together a Medium publication (https://medium.com/safenetwork34)
to collect the content in a single location. Medium brings with it an
additional virality that extends beyond our existing networks by tapping
into individual social networks (and also through regular email
updates). Moving forwards, we’d like to curate content about the Network
that’s posted on Medium (a good example is @goindeep’s recent posts). So if you create anything, please let @dugcampbell or @sarahpentland know.
Team meeting at HQ in April
MaidSafe employees are widely distributed around the globe, we’re keen
to bring the team together more regularly. To start this process, we’ve
arranged a weekend in April when everyone will descend on our Scottish
HQ so that we can brainstorm and build out a few strategies in person.
More on this to follow.
Finally, thanks for your support on the migration to r/safenetwork8.
We now have well over 1,000 readers and we’ll continue to focus on
growing this community each week. As a reminder, please support us by
subscribing to the subreddit - and also re-sharing any relevant articles
that you find elsewhere on r/safenetwork8.
SAFE Authenticator & API
We upgraded the system_uri library to the recently released v0.4.0 in safe_app_nodejs, and removed the libwinpthread.dll as a dynamic library dependency since it is now being statically linked in safe_app.dll. We also fixed some minor issues in the safe_app_nodejs documentation reported by @DaBrown95 (thanks, DaBrown95!). A new patch version of safe-node-app (v0.6.1) has been published on npmjs.com with these changes, and the updated documentation was also published at http://docs.maidsafe.net/safe_app_nodejs1.
is working on making sure the example apps can receive the
authorisation URI from the Authenticator even when they are launched in
dev mode. He has also been working on upgrading Node.js to v8.x on the
example apps as well as in safe_app_nodejs.
We are also working on adding a new function to the safe_app_nodejs API (already available in safe_app
lib) which allows the user to retrieve the list of containers, and
permissions granted for each of them, from an authorisation URI, i.e.
without the need to connect to the network to be able to retrieve such
just got back and he is fully focused on Peruse browser development.
We’ve had some initial design meetings to define the UI/UX to be
implemented in Peruse before we can officially release the first
version. In parallel to this, we keep fixing bugs and applying
enhancements to it.
The C# API has been progressing well. The
safe_app API implementation is ongoing and the authenticator bindings
are also being worked in parallel. Tests must be wired up to validate
the implementation before we start integrating it with the Xamarin
applications. As mentioned in last week’s dev update, improvements to
the C# API to make it more dev friendly have been implemented in the ongoing WIP branch1.
SAFE Client Libs
A couple of obscure bugs have been reported by the community2 member @jlpell
and the front-end team. We’re actively investigating and debugging both
of them: the first one concerns the app revocation procedure, which
previously had other issues which were fixed and covered with tests.
Now, the first look at it shows that this case is different, so we’re
trying to reconstruct the pre-conditions and the environment that lead
to this error. Another problem with SAFE Client Libs was discovered by @bochaco
and it causes memory errors and segmentation faults in some
circumstances. To get this fixed & covered, we’re also checking the
comprehensiveness of our test suite and looking for ways to extend and
After we get done with the fixes and the immediate
tasks, we’re planning to move the entire team to help with Routing
development. @adam has already joined it and @marcin and @nbaksalyar are currently catching up with the recent progress and documentation.
we’re also continuing with small improvements here and there. E.g.,
continuous integration build times started to get too long and
constantly failed with a timeout error which affected our workflow. We
split the build process into several stages which now run in parallel
and make build times more manageable.
Routing & Crust
Routing, we are still mostly fleshing out the flows for splits and
merges. A less complicated algorithm is now being aimed for. It is
anticipated that this refined approach shall cause less potential
issues, however, the edge cases still need to be considered to confirm
it’s viable, which is time-consuming and consists of many active
in-house discussions. Apart from that, work on the ageing simulation has
been restarted. We identified a number of issues that need to be
resolved, the biggest of which is making the simulated messages reflect
the proposal more closely. Current simulation code simplifies some
details of message flows a lot, which we suspect might be significant
for the results. The other issues are new features that we would like to
test, like using alternative relocation triggers or modifying some
minor details in the way peers age.
In Crust, we finally found out the issues with uTP connections. Actually, the problem was in the p2p crate with connection information exchange: it would simply timeout too soon - 20 seconds of being idle. For now the timeout value was extended,
but in the future, this could possibly be made configurable. The other
issue in Crust that made it so hard to debug this uTP problem was that
when p2p failed, it wouldn’t display an error.
Additionally, IGD was disabled for rendezvous/hole-punched connections.
That was redundant anyway because if we detect an IGD enabled device, we
can connect directly to it instead, which is more reliable. Also, we
did a fair amount of code refactoring, we fixed a lot of linting issues
and wrote more tests for both the p2p and crust
crates. All in all, during the past week we made a couple more steps
towards more robust peer-to-peer connections with Crust and it was
pretty fun to see peer-to-peer chat16 working - no intermediate servers, obscure cloud services, APIs, etc. just real, old-school networking