Cache, Blockstart, NEM - A Message From the CEO

My name is Mark Price and I am the CEO of a company called Devslopes.

When we found NEM we knew that we had found the blockchain platform that would take blockchain to the world.

It wasn’t overly apparent at first, but I’m a technologist and look deeply into the tech. NEM was a diamond in the rough.

That was months ago. Now we have officialy launched a token sale that is built on NEM Technology.

Cache Token Sale

This forum post isn't about promoting the Cache Token Sale. It is about explaining who we are, what we have done, what we are doing, and how this fits together in the NEM ecosystem.

This post is also in response to the great controversy that has arisen about this project in the NEMberia and NEM::Red Telegram groups.

Who We Are

I’ve owned a learn to code company named Devslopes since 2015. We have taught over 300,000 developers subjects such as React, Angular, iOS, Android, Game Development, and most recently blockchain.

We have 8 employees, are high energy, honest, and believe in community and decentralization. This is another reason why NEM is so appealing to us.

We are great developers and great trainers. We are passionate about learning and helping people better their lives, launch businesses, and create startups and apps.

Getting Started With NEM

I was introduced to NEM by a long term Devslopes customer and student and NEM advocate, El Boyd.


He told me I absolutely needed to check out NEM. It could change how developers work with blockchain. Give this guy some XEM.

I went to the NEM website - and was actually incredibly unimpressed. An intro video with flying clouds? The whole website felt rather corporate, and I couldn’t find any great getting started resources.

I talked to El - he said please keep trying. So I did.

I took a week off of my normal work week and did nothing but NEM.

A few days in, after much confusion due to outdated resources and conflicting paths to success I discovered NEM Library

Created by Aleix and guillem. If ANYONE at NEM should be awarded for their ability to make NEM accessible, it is these guys.

After writing some code and scouring the Internet for information about NEM and its technology, I finally saw the vision.

A diamond in the rough.

Things We’ve Done With NEM

My company Devslopes has now invested $38,400 in NEM initiatives. We’ve asked for nothing in return. We wanted to onboard developers into a platform we think IS a game changer.

Here are a few things we have done so far:

Again, have received nothing in return throughout this process. No expectations to receive anything. We love NEM.

And some people seem to like us:

Cache & Blockstart

I’m not going to go into detail on everything we are doing in this campaign.

You can read that in the white paper on

  • Cache is a token on the NEM public blockchain (NIS1)
  • We are building some SDKs to make working with Cache easy. These will all be working with NEM public blockchain (NIS1)
  • We are building a decentralized app called Cacheout. This will utilize Cache on the NEM public blockchain (NIS1)
  • The BIG project though is called Blockstart. Blockstart is a fork of Catapult.
  • Blockstart will have a B2B business that will let our customers launch their own Blockchain networks. This product does not involve NEM public blockchain (NIS1)
  • Blockstart will have its own public blockchain that uses Cache as its driving token. Blockstart will work with Cache that lives on the NEM public blockchain (NIS1) but Blockstart itself will not have any connection to the NEM public blockchain or XEM in regards to users paying XEM fees.
  • Blockstart B2B will accept XEM and Cache as forms of payment
  • We will develop a series of powerful SDKs that work on top of Blockstart (Catapult). These will all be open source.

See the image below for what those SDKs will do:

The Debate

Some people in the NEM community are very angry about the Blockstart Public Blockchain.

I never thought of this as controversial. In fact, I thought it complimentary and beneficial to NEM.

But here are a few of the concerns:

  • Blockstart is mainstream and for profit - that is not how blockchain should be, that is not what NEM stands for
  • Blockstart is frustrating because it might release before NEM Catapult public chain and de-value XEM
  • Some feel that NEM open sourced Catapult too soon - that Catapult should have come out with the launch of the NEM public blockchain on Catapult. This frustration is indirectly turned at Blockstart
  • Catapult should have a license that demands more recognition
  • Devslopes is being unethical by not building on top of the future NEM Catapult public blockchain.

Why does Blockstart exist?

Blockstart exists because we at Devslopes believe that blockchain needs to reach mass adoption. This will never happen with crypto fanatics nor with Ethereum.

It can only happen through developers and tools that make the features of blockchain easy to implement.

We saw this with NEM from day 1. We really wanted to move this forward. We were fueled with fire (and still are).

We made friends with multiple people at NEM Foundation (Official employees/members).

We explained some of our ideas on how we thought we could help NEM achieve aggressive, worldwide developer adoption and throw Ethereum into ancient history.

We sent multiple proposals over time, but I want to give you the BIG proposal that we thought could be a game changer:

View the Proposal

NEM decided that it would be unethical for NEM to bring on a company to help with this. It would show a form of favoritism and that wouldn’t be right for the community or ecosystem. Also NEM already had its Center of Excellence in the works.

I totally respect this decision. I get it 100%. It is admirable of them. We still had the support of some NEM decision makers, but it was apparent progress and opportunities might be slow.

Now what is a CEO to do? Especially a CEO who believes in NEM, and especially a CEO who is able to fork Catapult and build this dream of worldwide developer adoption of blockchain.

NEMbers We Have Worked With

This does not say they have endorsed or not endorsed us, but these are people who I have spoken to and who are aware of one or more of our proposals (some not aware of other proposals)

  • Alexandra
  • Jeff
  • Aleix
  • David
  • Albert
  • Stephen
  • Kristoff

Our Decision

This is where Blockstart fits in.

People are asking us, “Why can’t you just build all these great features on the future NEM public blockchain?”

Here are the reasons:

  1. Catapult for NEM public chain is not released yet
  2. There is no incentive for Devslopes to do that

We want to sprint fast. Also, we want to generate profits as any good business might do. If we built on NEM public blockchain we would make less money. I know this sounds harsh, but I don’t think it is unethical - maybe it’s not good for the market value of XEM (spoken by other people - not me), but its good for Devslopes.

Also I think its great for NEM. Publicity. More developers using their tech. We still are using it, so we still need to train on it.

My team is ready to code Also, now we have Cache token owners who will want the ability to use that token. Trade it. Sell it. The token’s success is directly tied to Blockstart.

Can Devslopes + NEM Work Together

Yes. I would love that. I would love to use whatever influence I and my team have to grow NEM, especially in the United States.

If I had a way to make this happen I would. I would build every feature that we are planning on NEM. I would help grow NEM North America, and spread NEM worldwide.

The reality is we have to keep moving, and we have to fund our development. Hence the Cache Token sale.

We are open to opportunities. We just want to work on NEM tech, monetize on it, and bring blockchain features to the world.

  • Mark Price CEO | Devslopes (Cache Token Sale)

It looks very interesting.
Just as a layman, could I ask a couple of questions?
This might also help a few of us that are not so savy on Block-chain programming or so technically minded.

  • In what way is Blockstart a fork of Catapult? ie Is it Catapult code redefined? (Not sure how since Catapult is not released yet Publicly) and if it does not reside on the Nem public chain (or private) then how in any way is it anything to do with Catapult?
    My understanding of a “fork” is when a group of developers working on one project go separate ways (fork) due to a conflict of ideas or strategy.
    Did any of your Devs work on Catapult?

  • What programming language will Blockstart be written in (C++)?

That’s all, my name says it all so I will not deluge you with any more of my questions.

I can understand your focus on building a developer community for Nem blockchain. I am sure there are a lot of resource for Devs on Nem, yet I see many coming here to this forum which imho is not a dedicated Blockchain Nem Dev site, sure we have experts here, yet I do not see a chronological knowledge base or a storage of knowledge and available updated resources for new Nem Devs arising from this forum.


Actually catapult SOURCE code is public already…

but it’s still looong road ahead before we’ll be able to switch public network from NIS1 to catapult.
Missing features are:

  • state cache for public chain (part of bison milestone)
  • changes in mosaic handling and fees
  • PoI (TBD)
  • state tree (also part of bison)
  • delegated harvesting and generally account properties - cow milestone

There’s much more, but that is bare minimum to have public chain switch


This happens all the time. In one hand we have good js libraries, dev courses on it and resources. But on the other hand NEM API is intended to be cross-platform, I tend to use python or go in accessing it even when I need to write my own libraries.
Still, I think NEM team should highlight the JS libraries more heavily as basically 90% of apps are based on it.

1 Like

When you fork code you are basically saying I’m going to make a copy of this code at this point in time, then add onto it.

When the original repository/code changes you can elect to pull those changes into your forked version.

We really don’t intend to change the core engine, though we think Proof of Importance could use some enhancements.

Concerning a Fork, we have clicked the “fork” button on Github which makes a copy of the code on our Github repository. Our version maintains a link (upstream) to the original code so we can take all the great changes made by the core team and upgrade the forked version.

Blockstart is built on Catapult. We will build SDKs on top of it in various languages and for various platforms (Swift, Kotlin, Unity 3D).

Devslopes/Blockstart did not work on nor contribute to Catapult.


Ok Thank you for your reply.
I can see now how some may have issues with it.
Since Catapult is open source there is no obligation for anyone choosing to utilise its features to actually implement it on the nem:xem network, hence not stimulating the xem price through volume or scarcity.

I myself even feel I would have liked to see this implemented on the nem public blockchain in this way.
Though that would be mainly due to myself not wanting my xem to become worthless and obsolete via the risk of creating an incentive of making more profit for companies, that incentive being to not actually use it (xem).

Though in saying that I can see a huge upside to teaching Nem and indeed increasing awareness throughout the blockchain programming community as Nem based projects and dapps face further mainstream adoption.
As I seen Lon once say “There is room for all to work together”.

I do like the idea of the Cacheout dapp, having spent some time on programming forums there is often a large amount of programmers that go unrewarded for very good information and often painstaking diligence in responding effectively to problems and issues faced by other programmers.
Just one example might be : It would be a great way for students to make some earnings on the side while studying.
The Cacheout websites look good.

I have not read the Blockstart paper yet but surely will.

BTW I am not on Telegram, so I had not heard of this project until I had actually read this topic. Actually I probably seen it on ‘inside Nem’ yet did not check it out properly.


1 Like

I’d like to point out something I noticed :

Looking at the GitHub orgs; starting with block start GitHub org appears to just be straight-up forks of NEM repos with no work done yet. A proper fork where the button ‘fork’ has been pressed just as @Mark_Price explains to @xemnewbie in an earlier comment how a fork works; it shows on the page it is a fork of NEM.

But on the Cache organisation where work has been done by the team; there is no forks; they have downloaded a zip of the repo (which doesn’t include the .git history) rather than actually pressing the ‘fork’ button (which is how he describes how a fork works).
On the nano wallet fork repo located here :

Here also is the NEM typescript SDK fork. Again in this instance a fork hasn’t been done as they describe they downloaded the code, made a 1 commit dump of all the files and then 1 more to remove all but one line of mention about NEM :


when will the POI be open source?
Thank you!

Hey gimer - you name some milestones “bison” and “cow” - are these listed somewhere? I’d love to learn more about them.