Topic: [ANN] [VELD] - Veldspar - A new type of coin, trying to solve different problems (Read 4374 times)
June 28, 2021, 11:33:56 AM
still a live ?
March 07, 2019, 09:50:20 AM
Are the devs still making progress on this?
Very ... very slowly. The pressure of family life and work leave little time to work on this projects. I have several major features functionally complete but they need a few hours to really shore them up for testing on a test net, plus a backlog of support requests.
I ams till hoping for help from other developers too! That would make a big difference.
March 05, 2019, 05:36:45 PM
Are the devs still making progress on this?
December 25, 2018, 04:57:10 PM
Glad to see you're still working on it. Is there a way to check my balance without a wallet at the moment?
Not yet, but i'm just testing an online web-wallet which will be read-only, with no transfers. I'll post here once it's up.
December 24, 2018, 04:58:02 PM
Glad to see you're still working on it. Is there a way to check my balance without a wallet at the moment?
December 12, 2018, 01:16:43 AM
So a bit of a status update on development, and that is that we are jumping straight to v0.2.0 in the roadmap and skipping 0.1.0 altogether.
What has been achieved:
1. Blockchain size and speed reduced and increased significantly.
2. Nodes will now be active for all functions, wallets and miners will connect to those local nodes and any changes to the blockchain will be broadcast to all connected nodes.
3. All nodes attempt to create and hash the blocks themselves but until 0.3.0 they will double check with the seed nodes that they have the correct data. Nodes which are not accessible from the outside world will always far and will always download block data from the swarm.
4. Generation of PoW is performed serially, so cannot be optimised with more cores/GPUs.
5. Data synchronisation is optimised to flow as fast as possible even if the nodes are underpowered, this will mean that regardless of state/stage transactions should remain atomic as all transactions are sequentially numbered and replayed.
6. Swapped to 1 min blocks to reduce the impact of a block being hashed and the time it takes.
7. Target inclusion is +30 blocks to give the network plenty of time to sync.
8. Difficulty is now super hard to reduce registration impact on the service.
What is outstanding before general release:
1.Memory leak in the sync mechanism needs resolving.
2. Transaction size when performing a transfer can become painfully huge, which is a basic design compromise of this system. This may not be resolved before release but will need to be looked into.
3. Windows wallet needs to be updated to use the new mechanism.
4. A public node will need to be made available for those unable to run Ubuntu 16/18.
5. Produce binaries for download of the wallet & miner.
6. Decide if the seed node will publish block data to a standard web server to be served up for wallets. This will avoid people having to run a node just to populate their wallet. Obviously this isn’t very de-centralised, but will offload one of the biggest
I have been struggling for time over the past few weeks, but just a few little niggles remain in the little bits of dev outstanding. Chief of which is the denominations system, which although solving some problems, causes others.
If we were to fix all tokens at `0.01` VELD, then to transfer 100 VELD to another wallet would require 10,000 new entries in the blockchain to be created. Which is quite heavy handed. Whereas if they are mixed, that transaction on average would be around 3,000 entries which is much better.
But you could also be left with a wallet full of 50.00 VELD tokens, so would be unable to transfer say 20.00 VELD to anyone.
So in that respect, the network also has to in the future (if this even becomes and issue) include some kind of “change” system/service which will be funded from the network fee collection pot.
But for the initial version it’s just something that needs to be worked around and the community members will just have to offer that service or, indeed I will if I can.
I’m looking forward to the release, if only so I don’t have to keep restarting the current service every couple of hours.
What has been achieved:
1. Blockchain size and speed reduced and increased significantly.
2. Nodes will now be active for all functions, wallets and miners will connect to those local nodes and any changes to the blockchain will be broadcast to all connected nodes.
3. All nodes attempt to create and hash the blocks themselves but until 0.3.0 they will double check with the seed nodes that they have the correct data. Nodes which are not accessible from the outside world will always far and will always download block data from the swarm.
4. Generation of PoW is performed serially, so cannot be optimised with more cores/GPUs.
5. Data synchronisation is optimised to flow as fast as possible even if the nodes are underpowered, this will mean that regardless of state/stage transactions should remain atomic as all transactions are sequentially numbered and replayed.
6. Swapped to 1 min blocks to reduce the impact of a block being hashed and the time it takes.
7. Target inclusion is +30 blocks to give the network plenty of time to sync.
8. Difficulty is now super hard to reduce registration impact on the service.
What is outstanding before general release:
1.
2. Transaction size when performing a transfer can become painfully huge, which is a basic design compromise of this system. This may not be resolved before release but will need to be looked into.
3. Windows wallet needs to be updated to use the new mechanism.
4. A public node will need to be made available for those unable to run Ubuntu 16/18.
5. Produce binaries for download of the wallet & miner.
6. Decide if the seed node will publish block data to a standard web server to be served up for wallets. This will avoid people having to run a node just to populate their wallet. Obviously this isn’t very de-centralised, but will offload one of the biggest
I have been struggling for time over the past few weeks, but just a few little niggles remain in the little bits of dev outstanding. Chief of which is the denominations system, which although solving some problems, causes others.
If we were to fix all tokens at `0.01` VELD, then to transfer 100 VELD to another wallet would require 10,000 new entries in the blockchain to be created. Which is quite heavy handed. Whereas if they are mixed, that transaction on average would be around 3,000 entries which is much better.
But you could also be left with a wallet full of 50.00 VELD tokens, so would be unable to transfer say 20.00 VELD to anyone.
So in that respect, the network also has to in the future (if this even becomes and issue) include some kind of “change” system/service which will be funded from the network fee collection pot.
But for the initial version it’s just something that needs to be worked around and the community members will just have to offer that service or, indeed I will if I can.
I’m looking forward to the release, if only so I don’t have to keep restarting the current service every couple of hours.
I stopped mining this a while ago. Will old coins be valid after new release?
Yes, all mining activity has been transferred.
December 11, 2018, 10:38:31 AM
So a bit of a status update on development, and that is that we are jumping straight to v0.2.0 in the roadmap and skipping 0.1.0 altogether.
What has been achieved:
1. Blockchain size and speed reduced and increased significantly.
2. Nodes will now be active for all functions, wallets and miners will connect to those local nodes and any changes to the blockchain will be broadcast to all connected nodes.
3. All nodes attempt to create and hash the blocks themselves but until 0.3.0 they will double check with the seed nodes that they have the correct data. Nodes which are not accessible from the outside world will always far and will always download block data from the swarm.
4. Generation of PoW is performed serially, so cannot be optimised with more cores/GPUs.
5. Data synchronisation is optimised to flow as fast as possible even if the nodes are underpowered, this will mean that regardless of state/stage transactions should remain atomic as all transactions are sequentially numbered and replayed.
6. Swapped to 1 min blocks to reduce the impact of a block being hashed and the time it takes.
7. Target inclusion is +30 blocks to give the network plenty of time to sync.
8. Difficulty is now super hard to reduce registration impact on the service.
What is outstanding before general release:
1.Memory leak in the sync mechanism needs resolving.
2. Transaction size when performing a transfer can become painfully huge, which is a basic design compromise of this system. This may not be resolved before release but will need to be looked into.
3. Windows wallet needs to be updated to use the new mechanism.
4. A public node will need to be made available for those unable to run Ubuntu 16/18.
5. Produce binaries for download of the wallet & miner.
6. Decide if the seed node will publish block data to a standard web server to be served up for wallets. This will avoid people having to run a node just to populate their wallet. Obviously this isn’t very de-centralised, but will offload one of the biggest
I have been struggling for time over the past few weeks, but just a few little niggles remain in the little bits of dev outstanding. Chief of which is the denominations system, which although solving some problems, causes others.
If we were to fix all tokens at `0.01` VELD, then to transfer 100 VELD to another wallet would require 10,000 new entries in the blockchain to be created. Which is quite heavy handed. Whereas if they are mixed, that transaction on average would be around 3,000 entries which is much better.
But you could also be left with a wallet full of 50.00 VELD tokens, so would be unable to transfer say 20.00 VELD to anyone.
So in that respect, the network also has to in the future (if this even becomes and issue) include some kind of “change” system/service which will be funded from the network fee collection pot.
But for the initial version it’s just something that needs to be worked around and the community members will just have to offer that service or, indeed I will if I can.
I’m looking forward to the release, if only so I don’t have to keep restarting the current service every couple of hours.
What has been achieved:
1. Blockchain size and speed reduced and increased significantly.
2. Nodes will now be active for all functions, wallets and miners will connect to those local nodes and any changes to the blockchain will be broadcast to all connected nodes.
3. All nodes attempt to create and hash the blocks themselves but until 0.3.0 they will double check with the seed nodes that they have the correct data. Nodes which are not accessible from the outside world will always far and will always download block data from the swarm.
4. Generation of PoW is performed serially, so cannot be optimised with more cores/GPUs.
5. Data synchronisation is optimised to flow as fast as possible even if the nodes are underpowered, this will mean that regardless of state/stage transactions should remain atomic as all transactions are sequentially numbered and replayed.
6. Swapped to 1 min blocks to reduce the impact of a block being hashed and the time it takes.
7. Target inclusion is +30 blocks to give the network plenty of time to sync.
8. Difficulty is now super hard to reduce registration impact on the service.
What is outstanding before general release:
1.
2. Transaction size when performing a transfer can become painfully huge, which is a basic design compromise of this system. This may not be resolved before release but will need to be looked into.
3. Windows wallet needs to be updated to use the new mechanism.
4. A public node will need to be made available for those unable to run Ubuntu 16/18.
5. Produce binaries for download of the wallet & miner.
6. Decide if the seed node will publish block data to a standard web server to be served up for wallets. This will avoid people having to run a node just to populate their wallet. Obviously this isn’t very de-centralised, but will offload one of the biggest
I have been struggling for time over the past few weeks, but just a few little niggles remain in the little bits of dev outstanding. Chief of which is the denominations system, which although solving some problems, causes others.
If we were to fix all tokens at `0.01` VELD, then to transfer 100 VELD to another wallet would require 10,000 new entries in the blockchain to be created. Which is quite heavy handed. Whereas if they are mixed, that transaction on average would be around 3,000 entries which is much better.
But you could also be left with a wallet full of 50.00 VELD tokens, so would be unable to transfer say 20.00 VELD to anyone.
So in that respect, the network also has to in the future (if this even becomes and issue) include some kind of “change” system/service which will be funded from the network fee collection pot.
But for the initial version it’s just something that needs to be worked around and the community members will just have to offer that service or, indeed I will if I can.
I’m looking forward to the release, if only so I don’t have to keep restarting the current service every couple of hours.
I stopped mining this a while ago. Will old coins be valid after new release?
December 05, 2018, 06:35:14 PM
So a bit of a status update on development, and that is that we are jumping straight to v0.2.0 in the roadmap and skipping 0.1.0 altogether.
What has been achieved:
1. Blockchain size and speed reduced and increased significantly.
2. Nodes will now be active for all functions, wallets and miners will connect to those local nodes and any changes to the blockchain will be broadcast to all connected nodes.
3. All nodes attempt to create and hash the blocks themselves but until 0.3.0 they will double check with the seed nodes that they have the correct data. Nodes which are not accessible from the outside world will always far and will always download block data from the swarm.
4. Generation of PoW is performed serially, so cannot be optimised with more cores/GPUs.
5. Data synchronisation is optimised to flow as fast as possible even if the nodes are underpowered, this will mean that regardless of state/stage transactions should remain atomic as all transactions are sequentially numbered and replayed.
6. Swapped to 1 min blocks to reduce the impact of a block being hashed and the time it takes.
7. Target inclusion is +30 blocks to give the network plenty of time to sync.
8. Difficulty is now super hard to reduce registration impact on the service.
What is outstanding before general release:
1.Memory leak in the sync mechanism needs resolving.
2. Transaction size when performing a transfer can become painfully huge, which is a basic design compromise of this system. This may not be resolved before release but will need to be looked into.
3. Windows wallet needs to be updated to use the new mechanism.
4. A public node will need to be made available for those unable to run Ubuntu 16/18.
5. Produce binaries for download of the wallet & miner.
6. Decide if the seed node will publish block data to a standard web server to be served up for wallets. This will avoid people having to run a node just to populate their wallet. Obviously this isn’t very de-centralised, but will offload one of the biggest
I have been struggling for time over the past few weeks, but just a few little niggles remain in the little bits of dev outstanding. Chief of which is the denominations system, which although solving some problems, causes others.
If we were to fix all tokens at `0.01` VELD, then to transfer 100 VELD to another wallet would require 10,000 new entries in the blockchain to be created. Which is quite heavy handed. Whereas if they are mixed, that transaction on average would be around 3,000 entries which is much better.
But you could also be left with a wallet full of 50.00 VELD tokens, so would be unable to transfer say 20.00 VELD to anyone.
So in that respect, the network also has to in the future (if this even becomes and issue) include some kind of “change” system/service which will be funded from the network fee collection pot.
But for the initial version it’s just something that needs to be worked around and the community members will just have to offer that service or, indeed I will if I can.
I’m looking forward to the release, if only so I don’t have to keep restarting the current service every couple of hours.
What has been achieved:
1. Blockchain size and speed reduced and increased significantly.
2. Nodes will now be active for all functions, wallets and miners will connect to those local nodes and any changes to the blockchain will be broadcast to all connected nodes.
3. All nodes attempt to create and hash the blocks themselves but until 0.3.0 they will double check with the seed nodes that they have the correct data. Nodes which are not accessible from the outside world will always far and will always download block data from the swarm.
4. Generation of PoW is performed serially, so cannot be optimised with more cores/GPUs.
5. Data synchronisation is optimised to flow as fast as possible even if the nodes are underpowered, this will mean that regardless of state/stage transactions should remain atomic as all transactions are sequentially numbered and replayed.
6. Swapped to 1 min blocks to reduce the impact of a block being hashed and the time it takes.
7. Target inclusion is +30 blocks to give the network plenty of time to sync.
8. Difficulty is now super hard to reduce registration impact on the service.
What is outstanding before general release:
1.
2. Transaction size when performing a transfer can become painfully huge, which is a basic design compromise of this system. This may not be resolved before release but will need to be looked into.
3. Windows wallet needs to be updated to use the new mechanism.
4. A public node will need to be made available for those unable to run Ubuntu 16/18.
5. Produce binaries for download of the wallet & miner.
6. Decide if the seed node will publish block data to a standard web server to be served up for wallets. This will avoid people having to run a node just to populate their wallet. Obviously this isn’t very de-centralised, but will offload one of the biggest
I have been struggling for time over the past few weeks, but just a few little niggles remain in the little bits of dev outstanding. Chief of which is the denominations system, which although solving some problems, causes others.
If we were to fix all tokens at `0.01` VELD, then to transfer 100 VELD to another wallet would require 10,000 new entries in the blockchain to be created. Which is quite heavy handed. Whereas if they are mixed, that transaction on average would be around 3,000 entries which is much better.
But you could also be left with a wallet full of 50.00 VELD tokens, so would be unable to transfer say 20.00 VELD to anyone.
So in that respect, the network also has to in the future (if this even becomes and issue) include some kind of “change” system/service which will be funded from the network fee collection pot.
But for the initial version it’s just something that needs to be worked around and the community members will just have to offer that service or, indeed I will if I can.
I’m looking forward to the release, if only so I don’t have to keep restarting the current service every couple of hours.
November 04, 2018, 08:06:55 AM
Astonishing concept 
I will mine this.
I will mine this. 
October 21, 2018, 06:54:06 AM
Hopefully this will add a bit of perspective and focus.
https://medium.com/@napoleonbonafrog/whats-the-point-why-bother-d04089ea724f
https://medium.com/@napoleonbonafrog/whats-the-point-why-bother-d04089ea724f
Thanks, it's definitely a good read and I like the humanitarian focus that you're putting on the project without leaving out the economics altogether.
October 20, 2018, 03:59:49 PM
Hopefully this will add a bit of perspective and focus.
https://medium.com/@napoleonbonafrog/whats-the-point-why-bother-d04089ea724f
https://medium.com/@napoleonbonafrog/whats-the-point-why-bother-d04089ea724f
October 08, 2018, 08:06:07 PM
Any idea when transactions will be enabled? Maybe it's too soon for this but it would be nice to at least have some otc trading available.
if in my opinion, it's better to be activated immediately so that many people have otc trading, sir. if it is too long, fear will be delayed and there will be many obstacles. of course it's very uncomfortableThere has been much re-work of the codebase, transactions have been completed but as of yet we have not made a release to production. So, there will be another release, along with the much planned re-boot of the blockchain and this will be within the next 2 weeks.
That's great! thanks for the update and for all the work you do on the project, it's hard to come by projects that are built from scratch these days.
October 08, 2018, 03:13:50 AM
Any idea when transactions will be enabled? Maybe it's too soon for this but it would be nice to at least have some otc trading available.
if in my opinion, it's better to be activated immediately so that many people have otc trading, sir. if it is too long, fear will be delayed and there will be many obstacles. of course it's very uncomfortableThere has been much re-work of the codebase, transactions have been completed but as of yet we have not made a release to production. So, there will be another release, along with the much planned re-boot of the blockchain and this will be within the next 2 weeks.
October 07, 2018, 08:08:43 PM
Any idea when transactions will be enabled? Maybe it's too soon for this but it would be nice to at least have some otc trading available.
if in my opinion, it's better to be activated immediately so that many people have otc trading, sir. if it is too long, fear will be delayed and there will be many obstacles. of course it's very uncomfortable October 07, 2018, 07:59:35 PM
From what I read in these last paragraphs in the ANN initial post, can it only be mined on these platforms described? For windows have any position?
You can only run the wallet on linux for now, but there is already a miner that works on Windows.
October 07, 2018, 07:19:55 PM
From what I read in these last paragraphs in the ANN initial post, can it only be mined on these platforms described? For windows have any position?
October 07, 2018, 07:03:13 PM
Any idea when transactions will be enabled? Maybe it's too soon for this but it would be nice to at least have some otc trading available.
September 24, 2018, 01:04:37 PM
If not a secret how many people in the team? Or do you work alone? As it seems to me it is necessary to hire more managers on work with the community otherwise there will be gaps in the answers and in communication. When there are no replies and the team disappears, there immediately appears a fool that the project has closed.
It is just me with a couple of extra devs working on things like wallets, API services and some of the P2P network design. We are always recruiting for more, but it's early days and lots to do. I think PR is a problem when you have more than a handful of miners to deal with.
I am pretty active on Discord which is our main interface to the world.
September 24, 2018, 06:01:43 AM
If not a secret how many people in the team? Or do you work alone? As it seems to me it is necessary to hire more managers on work with the community otherwise there will be gaps in the answers and in communication. When there are no replies and the team disappears, there immediately appears a fool that the project has closed.
September 24, 2018, 03:39:01 AM
Yes and no, I am always busy on other things, but actually this has turned out to be quite a bit of work. And since i'm in that place I decided to make other changes that would help in the future too. Fixing the build on Ubuntu 18 seemed like a good idea, removing dependencies on uncommon libs etc....
I did also contemplate a re-write into c/c++, but actually as swift support spreads the issues of deployment will go away.
Having discussed the project at great length, there are also other changes we will make. The whole "design" for exchange mentality needs to stop, as the coins provide no purpose and little benefit for humanity. The "Ore" system, provides an opportunity to change that and to have real value and reward for humanity, but will not necessarily fit with the ideals of money markets. But that is all future thoughts.
I did also contemplate a re-write into c/c++, but actually as swift support spreads the issues of deployment will go away.
Having discussed the project at great length, there are also other changes we will make. The whole "design" for exchange mentality needs to stop, as the coins provide no purpose and little benefit for humanity. The "Ore" system, provides an opportunity to change that and to have real value and reward for humanity, but will not necessarily fit with the ideals of money markets. But that is all future thoughts.
Jump to: