Blockhain start-up Vaionex is leading the charge to restore the old Bitcoin SV developers site to act as a comprehensive landing page for the Bitcoin SV developer community. We sat down with Kohze to find out why the time was right to reinvigorate this project and what he hopes to achieve as a result.
The BitcoinSVDevelopers.com domain was originally set up as a rudimentary info-hub for Bitcoin SV, but the then-owner did not maintain the site and it had been offline for some months by the time it was gifted to Vaionex and its founder, Robin Kohze.
‘Instead of buying the domain, we inherited it from the original owner with the wish to bring it back to life,’ Kohze explains.
‘Since the platform was already a brand name within the community, we saw a chance to restore its original strengths.’
In line with Vaionex’s other ventures, the site aims to be a hub for all things related to Bitcoin SV development, especially for the developer community.
‘We are an infrastructure provider, which means the more developers we onboard to the ecosystem, the more we can ultimately do for them. We consider having such platforms a win-win situation that every infrastructure company in the space will benefit from,’ he says.
‘We liked the fact that there was one platform [the old website] that you can send someone who is completely new to the ecosystem, to pick them up from wherever they’re starting from, and then say, “here are these resources, here’s what you can do with Bitcoin SV and here are the people working on it now”.’
Rebuilding from the ground up
The original website itself was basic. Built on PHP and lacking any user interactivity, there was very little for the incoming owners to work with, so the new platform had to be built from the ground up.
‘It’s kind of like taking over an old house which is falling apart so that you can make it new again,’ says Kohze.
‘We tried to be as impartial as possible when building the platform, adding every perspective of development to the site. As a company, we don’t think we can nor should capture everything – and rather see ourselves as participants within the greater ecosystem that provide a gateway into development and provide critical infrastructure to deliver working products.’
The idea is for the content on the site to be community-driven, with some input from moderators who will be drawn from the community at large.
‘What makes us unique is that we will invite leading members from the ecosystem to serve as moderators,’ explains Kohze.
‘We think there are always people coming and going, and people who have more insights and people who have less insights into new developments,’
For example, the site’s tools and services page is divided into a range of category heads, each containing specific resources for users to browse and draw from. The order of these resources changes based on the popularity of each individual library and service.
‘If we are going to exponentially grow as an ecosystem, it doesn’t make sense to have the presence or absence of specific developer libraries completely controlled by somebody deciding which is the most important or the second most important resource,’ Kohze adds.
‘You need to have systems that self-manage, for instance by pushing up what is popular, and what is popular is decided by the community.’
A directory for Bitcoin SV developers
Every user has their own user page connected to the specific tools they have experience with, allowing for the community to easily connect with other members with similar interests in addition to functioning as a repository of developers for those looking to add expertise to their own projects. For example, a person hiring for a Bitcoin SV project can run a search for all developers with expertise in Satolearn, or all developers who have contributed to MoneyButton in the past. This is the level of integration that Kohze and Vaionex hope to achieve with the site, adding value at multiple points throughout the ecosystem.
Looking ahead to the future for the website, Kohze says that the project’s attention will remain fixed on the community.
‘There are certainly opportunities to try to connect closer to the industry by integrating our tools with each other and with the community – for example, creating a tool which allows industry to recruit their members. Then, if I am a recruiter, I could use the site to see the top developers for a particular project, which will be linked to their profile and GitHub page, allowing me see who the top contributors are just based on how many lines of code they contributed,’ he said.
‘Then, we become an essential data source for making decisions on who to recruit because you see the whole ecosystem: who are the top developers? Who of the top developers are open to being recruited based on their profile settings? That will be a tool that likely will bind together the whole community in a better way.’