Topic: Bitmark - page 24. (Read 622228 times)
Any news on the poloniex wallet, has been in maintenance for months.
06 / 12
no roadmap no future plan?
no roadmap no future plan?
It will be announced soon.Bitmark is waiting for a nice pump.
Will be glad to see new roadmap for bitmark. Its good project, but devs need to do more promotion for the coin.
06 / 12
no roadmap no future plan?
no roadmap no future plan?
It will be announced soon.Bitmark is waiting for a nice pump.
06 / 12
no roadmap no future plan?
no roadmap no future plan?
tl;dr
Is part of this proposal to roll back all rewards since the 51%?
That would bring back a lot of interest and faith in this project...
As it stands, the looming idea is that massive bag is going to be dumped on the exchange as soon as deposits are allowed.
Is part of this proposal to roll back all rewards since the 51%?
That would bring back a lot of interest and faith in this project...
As it stands, the looming idea is that massive bag is going to be dumped on the exchange as soon as deposits are allowed.
It's an idea worth considering, but it has many implications. Coins generated after the 51% might well be in innocent people's hands by now; invalidating those coins would be counter-productive.
Regarding the quote below - I read VRM - verium reserve got an algo that protects from asic and gpu mining and enables it for all people with CPU. Maybe worth checking what they did.
PS
What about switching to KMD childchain? Would that be possible and give any advantage or problems?
That would require some snapshot or sth... But would be part of a bigger project and inherit some good properties maybe ?
iii) Multiple Proof-of-Work Algorithms: (mPOW)
The single thing which allows a particular group to selfishly orphan blocks is overwhelming computational advantage in Bitmark's originally-chosen Proof-of-Work algorithm, SCrypt. By adopting additional Proof-of-Work algorithms, or a single composite (composed of several sequential PoW algos) algorithm [such as X11, X17 or Lyra2REv2] the 51% exploiters are denied the ability to abuse their computational advantage. Further, by implementing new PoW algorithms which have not been implemented in hardware ASICs, such as Argon2, the mining field is leveled and extended to miners with popular and common GPU or CPU equipment.
In our case, we propose to add 4 additional Proof-of-Work algorithms, which may contribute and add blocks to the Bitmark blockchain, for a total of 5 Proof-of-Work algorithms. One additional single PoW algo is the well-established SHA256D algorithm employed by Bitcoin. The reason to add this algo is to broaden Bitmark's appeal to the huge installed base of miners, which have SHA256D specific hardware. Another single PoW algo is the cutting-edge Argon2 algorithm, chosen because it is a winner in the 2015 Password Hashing Competition and because as of yet, there are no known ASIC implementations of it. One chained composite PoW algo chosen is Lyra2REv2, used by Vertcoin. Vertcoin has a demonstrated track record and commitment to de-centralized mining. We choose to bank on this proven and successful algorithm. Lastly, another composite chained PoW algo, X17, extends the idea pioneered by Dash, which itself uses the X11 composite chained PoW algorithm, by adding an additional 6 components to X11
PS
What about switching to KMD childchain? Would that be possible and give any advantage or problems?
That would require some snapshot or sth... But would be part of a bigger project and inherit some good properties maybe ?
iii) Multiple Proof-of-Work Algorithms: (mPOW)
The single thing which allows a particular group to selfishly orphan blocks is overwhelming computational advantage in Bitmark's originally-chosen Proof-of-Work algorithm, SCrypt. By adopting additional Proof-of-Work algorithms, or a single composite (composed of several sequential PoW algos) algorithm [such as X11, X17 or Lyra2REv2] the 51% exploiters are denied the ability to abuse their computational advantage. Further, by implementing new PoW algorithms which have not been implemented in hardware ASICs, such as Argon2, the mining field is leveled and extended to miners with popular and common GPU or CPU equipment.
In our case, we propose to add 4 additional Proof-of-Work algorithms, which may contribute and add blocks to the Bitmark blockchain, for a total of 5 Proof-of-Work algorithms. One additional single PoW algo is the well-established SHA256D algorithm employed by Bitcoin. The reason to add this algo is to broaden Bitmark's appeal to the huge installed base of miners, which have SHA256D specific hardware. Another single PoW algo is the cutting-edge Argon2 algorithm, chosen because it is a winner in the 2015 Password Hashing Competition and because as of yet, there are no known ASIC implementations of it. One chained composite PoW algo chosen is Lyra2REv2, used by Vertcoin. Vertcoin has a demonstrated track record and commitment to de-centralized mining. We choose to bank on this proven and successful algorithm. Lastly, another composite chained PoW algo, X17, extends the idea pioneered by Dash, which itself uses the X11 composite chained PoW algorithm, by adding an additional 6 components to X11
!!!New OTC exchange for blocked-on-exchanges currencies!!!
I am pleased to announce that I'm starting a new OTC exchange project for blocked-on-exchanges currencies all over the world.
This is a P2P centralized space where holders of different blocked-on-exchange currencies come together to trade for USD or against each other.
My inspiration comes from hearing about the banned currencies based on cryptonote protocol, which were deemed to be untradable by several leading exchange platforms.
I came up with the idea to create a OTC lifeline for these blocked-on-exchange currencies. And now I invite everyone who needs to change and transfer their blocked-on-exchange coin to try my service!
Guarantee:
I will act as the sole middleman holding all incoming deals, which will be verified from the both sides via email and skype. The transaction is 100% secure and does not require an ID.
If you don't feel comfortable exchanging through me, we can use any other trustworthy party from trusted bitcointalk member who will take part in the entire process.
Terms of Exchange:
Minimum transaction amount - $500
Fee - 1% from the deal
Write me to know more!
I am pleased to announce that I'm starting a new OTC exchange project for blocked-on-exchanges currencies all over the world.
This is a P2P centralized space where holders of different blocked-on-exchange currencies come together to trade for USD or against each other.
My inspiration comes from hearing about the banned currencies based on cryptonote protocol, which were deemed to be untradable by several leading exchange platforms.
I came up with the idea to create a OTC lifeline for these blocked-on-exchange currencies. And now I invite everyone who needs to change and transfer their blocked-on-exchange coin to try my service!
Guarantee:
I will act as the sole middleman holding all incoming deals, which will be verified from the both sides via email and skype. The transaction is 100% secure and does not require an ID.
If you don't feel comfortable exchanging through me, we can use any other trustworthy party from trusted bitcointalk member who will take part in the entire process.
Terms of Exchange:
Minimum transaction amount - $500
Fee - 1% from the deal
Write me to know more!
tl;dr
Is part of this proposal to roll back all rewards since the 51%?
That would bring back a lot of interest and faith in this project...
As it stands, the looming idea is that massive bag is going to be dumped on the exchange as soon as deposits are allowed.
Is part of this proposal to roll back all rewards since the 51%?
That would bring back a lot of interest and faith in this project...
As it stands, the looming idea is that massive bag is going to be dumped on the exchange as soon as deposits are allowed.
This makes sense to me at first look. Do we know how many coins the hijacker has managed to hoard? You'd need to know the last time anyone else was able to mine blocks.
tl;dr
Is part of this proposal to roll back all rewards since the 51%?
That would bring back a lot of interest and faith in this project...
As it stands, the looming idea is that massive bag is going to be dumped on the exchange as soon as deposits are allowed.
Is part of this proposal to roll back all rewards since the 51%?
That would bring back a lot of interest and faith in this project...
As it stands, the looming idea is that massive bag is going to be dumped on the exchange as soon as deposits are allowed.
Hard Fork Proposal:
Introduction
The bar for a hard fork in crypto currency should be set high. The reason is that a hard fork runs the risk of creating two chains and potentially damaging the currency. Both ethereum and bitcoin have had failed hard forks, despite their large communities. Therefore, to ensure that stakeholders do not lose their assets, any hard fork for bitmark should have the best possible planning. The following is a recap of the issues that Bitmark is facing and the proposed solutions. Input is welcome.
1. The problems
This should be ideally understandable to a wide audience.
i) Hash rate Swings.
Hash rate swings (which have been observed to go from a few MH/s to over 100 GH/s) result in a difficulty factor either much too high (which results in no blocks being found and thus no transactions processed, sometimes for as long as several days !) or too low (blocks being too quickly, within seconds of each other). This is the direct result of a difficulty adjustment algorithm, which only takes action every 720 found blocks. This is much too unresponsive. Users of the coin have a reasonable expectation that their transactions will be processed and validated quickly. The advertised inter-block time for bitmark is 2 minutes.
ii) Coin Emission exceeding Demand.
When a healthy block chain generates more coins than the market's ability to absorb these coins, the price per coin will naturally go down (whether denominated in bitcoins, dollars, pounds, yuan or another alt-coin). This is not desirable for stakeholders and supporters of the coin. While the continuous difficulty-adjustment algorithms fix the problem of transactions not being processed expediently, they bring an unwanted side effect: too many coins being generated.
iii) ≥ 51% Hash Rate Attacks.
Excessive number of Orphaned Blocks.
Blockchain Anomalies.
Suspension of Withdrawals and Deposits on Crypto Currency Exchanges.
Many longtime miners have abandoned mining Bitmark (BTM) because a some mining syndicate, commanding enough SCrypt hash power, has been able to privately build on the Bitmark blockchain, and strategically and "selfishly" publish to the rest of the Bitmark network 'their' chain, which is necessarily longer than any competing chain, only when it suits them, thus orphaning and wasting all the work of all the other miners. This problem has to do with the 720 block maturity requirement for generated coins to be used. Miners have to wait 720 blocks before they can spend the coins in a block they have mined. This 'selfish' syndicate is able to act this way because it must have an overwhelming computational advantage in SCrypt hash power. The kind of manipulation, which the bitmark chain has experienced lately, is in fact a type of 51% attack.
There have been reports on BitcoinTalk.org of double-spends related to forked chains. These excessively long chain forks and the abuses they enable are most likely behind the suspension of Bitmark deposits and withdrawals both on Nova and the Poloniex crypto currency exchanges.
iv) Marking Facilities.
Making Bitmark the premiere choice for marking applications.
It has often been asked what distinguishes Bitmark from other blockchain technologies, what advantage it has in regards to the many use cases of marking and related digital notarization applications.
2. The Proposed Solutions
Again this should be widely understood. There should also be a section explaining the risks.
The solutions:
i) Responsive Mining Difficulty Adjustment: Dark Gravity Wave, version 3 (DGWv3)
Difficulty adjustment algorithms, which re-set difficult upon each new block, were pioneered by Megacoin (Kimoto's Gravity Well), perfected by Dash (Dark Gravity Wave v3) and are now well established and standard in the alt-coin space. Bitcoin itself has not adopted any of these continuously difficulty-adjusting algorithms simply because bitcoin has never suffered from the wild network hash rate swings that alt-coins experience. In general terms, the hash rate on the bitcoin network has only every grown and increased.
ii) Demand Sensitive Coin Emission Modulation: (CEMv0.1)
By keeping track of the highest hash rate experienced recently (we choose 1 year as a look-back time frame) and equating this high hash rate with a demand level for the coin which warrants the epoch's highest possible level of coin generation, we hope to let coin generation match demand, and so maintain a more stable market value for the coin.
Most coins, including bitmark, were launched with a schedule of coin generation, which reduces the block reward at certain pre-set fixed number of blocks. These schedules define epochs where block rewards are at certain amounts. This rewards the early miners and first adopters with larger block rewards.
(Bitmark uses a quartering system, so, for bitmark, the first few block reward epochs are the 20 BTM, 15 BTM, 10 BTM, 7.5 BTM and 5 BTM epochs - Bitmark is currently in the first, or 20 BTM epoch; for bitcoin which uses a halving system, the epochs are 50 BTC, 25 BTC, 12.5 BTC, 6.25 BTC and 3.125 BTC - Bitcoin is currently in the 12.5 BTC epoch)
We maintain this basic epoch emission scheme, but refine it further, by allowing the current hash rate to affect coin generation, (instead of just the reaching of fixed block height milestones) Block reward is reduced from the epoch's full value if the current hash rate is lower than the highest hash rate seen within the last year. Block rewards are set for 1 day periods by comparing the current hash rate [] to the highest hash rate observed within one prior year and setting the reward proportionately. We thus decouple coin emission from block production, allowing for timely and expedient transaction processing without flooding the market with coins it is unable to absorb.
Now, the need to process transactions quickly does not mean that too many coins will be generated, because coin generation is informed and guided by demand, as expressed by hash rate. Care is taken to track total coins emitted (the money supply) because the original epoch reductions will be reached as a function of coins emitted, and not simply as a function of fixed block height milestones.
iii) Multiple Proof-of-Work Algorithms: (mPOW)
The single thing which allows a particular group to selfishly orphan blocks is overwhelming computational advantage in Bitmark's originally-chosen Proof-of-Work algorithm, SCrypt. By adopting additional Proof-of-Work algorithms, or a single composite (composed of several sequential PoW algos) algorithm [such as X11, X17 or Lyra2REv2] the 51% exploiters are denied the ability to abuse their computational advantage. Further, by implementing new PoW algorithms which have not been implemented in hardware ASICs, such as Argon2, the mining field is leveled and extended to miners with popular and common GPU or CPU equipment.
In our case, we propose to add 4 additional Proof-of-Work algorithms, which may contribute and add blocks to the Bitmark blockchain, for a total of 5 Proof-of-Work algorithms. One additional single PoW algo is the well-established SHA256D algorithm employed by Bitcoin. The reason to add this algo is to broaden Bitmark's appeal to the huge installed base of miners, which have SHA256D specific hardware. Another single PoW algo is the cutting-edge Argon2 algorithm, chosen because it is a winner in the 2015 Password Hashing Competition and because as of yet, there are no known ASIC implementations of it. One chained composite PoW algo chosen is Lyra2REv2, used by Vertcoin. Vertcoin has a demonstrated track record and commitment to de-centralized mining. We choose to bank on this proven and successful algorithm. Lastly, another composite chained PoW algo, X17, extends the idea pioneered by Dash, which itself uses the X11 composite chained PoW algorithm, by adding an additional 6 components to X11
iv) Blockchain Anchored Data.
Anchoring data trees on transactions on the bitmark block chain using the chainpoint technology inexpensively provides irrefutable proof that the anchored data existed at that point in time. The interested parties must maintain the actual data, but hash functions provide the means to easily prove that the digital data existed as presented at that time.
Introduction
The bar for a hard fork in crypto currency should be set high. The reason is that a hard fork runs the risk of creating two chains and potentially damaging the currency. Both ethereum and bitcoin have had failed hard forks, despite their large communities. Therefore, to ensure that stakeholders do not lose their assets, any hard fork for bitmark should have the best possible planning. The following is a recap of the issues that Bitmark is facing and the proposed solutions. Input is welcome.
1. The problems
This should be ideally understandable to a wide audience.
i) Hash rate Swings.
Hash rate swings (which have been observed to go from a few MH/s to over 100 GH/s) result in a difficulty factor either much too high (which results in no blocks being found and thus no transactions processed, sometimes for as long as several days !) or too low (blocks being too quickly, within seconds of each other). This is the direct result of a difficulty adjustment algorithm, which only takes action every 720 found blocks. This is much too unresponsive. Users of the coin have a reasonable expectation that their transactions will be processed and validated quickly. The advertised inter-block time for bitmark is 2 minutes.
ii) Coin Emission exceeding Demand.
When a healthy block chain generates more coins than the market's ability to absorb these coins, the price per coin will naturally go down (whether denominated in bitcoins, dollars, pounds, yuan or another alt-coin). This is not desirable for stakeholders and supporters of the coin. While the continuous difficulty-adjustment algorithms fix the problem of transactions not being processed expediently, they bring an unwanted side effect: too many coins being generated.
iii) ≥ 51% Hash Rate Attacks.
Excessive number of Orphaned Blocks.
Blockchain Anomalies.
Suspension of Withdrawals and Deposits on Crypto Currency Exchanges.
Many longtime miners have abandoned mining Bitmark (BTM) because a some mining syndicate, commanding enough SCrypt hash power, has been able to privately build on the Bitmark blockchain, and strategically and "selfishly" publish to the rest of the Bitmark network 'their' chain, which is necessarily longer than any competing chain, only when it suits them, thus orphaning and wasting all the work of all the other miners. This problem has to do with the 720 block maturity requirement for generated coins to be used. Miners have to wait 720 blocks before they can spend the coins in a block they have mined. This 'selfish' syndicate is able to act this way because it must have an overwhelming computational advantage in SCrypt hash power. The kind of manipulation, which the bitmark chain has experienced lately, is in fact a type of 51% attack.
There have been reports on BitcoinTalk.org of double-spends related to forked chains. These excessively long chain forks and the abuses they enable are most likely behind the suspension of Bitmark deposits and withdrawals both on Nova and the Poloniex crypto currency exchanges.
iv) Marking Facilities.
Making Bitmark the premiere choice for marking applications.
It has often been asked what distinguishes Bitmark from other blockchain technologies, what advantage it has in regards to the many use cases of marking and related digital notarization applications.
2. The Proposed Solutions
Again this should be widely understood. There should also be a section explaining the risks.
The solutions:
i) Responsive Mining Difficulty Adjustment: Dark Gravity Wave, version 3 (DGWv3)
Difficulty adjustment algorithms, which re-set difficult upon each new block, were pioneered by Megacoin (Kimoto's Gravity Well), perfected by Dash (Dark Gravity Wave v3) and are now well established and standard in the alt-coin space. Bitcoin itself has not adopted any of these continuously difficulty-adjusting algorithms simply because bitcoin has never suffered from the wild network hash rate swings that alt-coins experience. In general terms, the hash rate on the bitcoin network has only every grown and increased.
ii) Demand Sensitive Coin Emission Modulation: (CEMv0.1)
By keeping track of the highest hash rate experienced recently (we choose 1 year as a look-back time frame) and equating this high hash rate with a demand level for the coin which warrants the epoch's highest possible level of coin generation, we hope to let coin generation match demand, and so maintain a more stable market value for the coin.
Most coins, including bitmark, were launched with a schedule of coin generation, which reduces the block reward at certain pre-set fixed number of blocks. These schedules define epochs where block rewards are at certain amounts. This rewards the early miners and first adopters with larger block rewards.
(Bitmark uses a quartering system, so, for bitmark, the first few block reward epochs are the 20 BTM, 15 BTM, 10 BTM, 7.5 BTM and 5 BTM epochs - Bitmark is currently in the first, or 20 BTM epoch; for bitcoin which uses a halving system, the epochs are 50 BTC, 25 BTC, 12.5 BTC, 6.25 BTC and 3.125 BTC - Bitcoin is currently in the 12.5 BTC epoch)
We maintain this basic epoch emission scheme, but refine it further, by allowing the current hash rate to affect coin generation, (instead of just the reaching of fixed block height milestones) Block reward is reduced from the epoch's full value if the current hash rate is lower than the highest hash rate seen within the last year. Block rewards are set for 1 day periods by comparing the current hash rate [] to the highest hash rate observed within one prior year and setting the reward proportionately. We thus decouple coin emission from block production, allowing for timely and expedient transaction processing without flooding the market with coins it is unable to absorb.
Now, the need to process transactions quickly does not mean that too many coins will be generated, because coin generation is informed and guided by demand, as expressed by hash rate. Care is taken to track total coins emitted (the money supply) because the original epoch reductions will be reached as a function of coins emitted, and not simply as a function of fixed block height milestones.
iii) Multiple Proof-of-Work Algorithms: (mPOW)
The single thing which allows a particular group to selfishly orphan blocks is overwhelming computational advantage in Bitmark's originally-chosen Proof-of-Work algorithm, SCrypt. By adopting additional Proof-of-Work algorithms, or a single composite (composed of several sequential PoW algos) algorithm [such as X11, X17 or Lyra2REv2] the 51% exploiters are denied the ability to abuse their computational advantage. Further, by implementing new PoW algorithms which have not been implemented in hardware ASICs, such as Argon2, the mining field is leveled and extended to miners with popular and common GPU or CPU equipment.
In our case, we propose to add 4 additional Proof-of-Work algorithms, which may contribute and add blocks to the Bitmark blockchain, for a total of 5 Proof-of-Work algorithms. One additional single PoW algo is the well-established SHA256D algorithm employed by Bitcoin. The reason to add this algo is to broaden Bitmark's appeal to the huge installed base of miners, which have SHA256D specific hardware. Another single PoW algo is the cutting-edge Argon2 algorithm, chosen because it is a winner in the 2015 Password Hashing Competition and because as of yet, there are no known ASIC implementations of it. One chained composite PoW algo chosen is Lyra2REv2, used by Vertcoin. Vertcoin has a demonstrated track record and commitment to de-centralized mining. We choose to bank on this proven and successful algorithm. Lastly, another composite chained PoW algo, X17, extends the idea pioneered by Dash, which itself uses the X11 composite chained PoW algorithm, by adding an additional 6 components to X11
iv) Blockchain Anchored Data.
Anchoring data trees on transactions on the bitmark block chain using the chainpoint technology inexpensively provides irrefutable proof that the anchored data existed at that point in time. The interested parties must maintain the actual data, but hash functions provide the means to easily prove that the digital data existed as presented at that time.
Any news from the devs? His last post was on 2015 lol
We are working on a hard fork proposal: https://github.com/project-bitmark/bitmark/wiki/Hard_Fork_Criteria
The proposed hard fork code is taking shape on the 0.9.7 branch of: https://github.com/piratelinux/bitmark
~dbKeys
Any news from the devs? His last post was on 2015 lol
hello
I am new to mining bitmark, and I can't find any full guides how to start mining on Windows. I have already started bitmarkd with config
But I can't find correct Scrypt software to use it with this. And official wiki says only
Can you give some recomendations on mining software installing and usage, please? And example, maybe?
I am new to mining bitmark, and I can't find any full guides how to start mining on Windows. I have already started bitmarkd with config
Code:
rpcuser=...
rpcpassword=...
rpcallowip=192.*.*.* (was 192.168.1.*, didn't work either)
daemon=1
server=1
alertnotify=echo %s
Quote
Launch your preferred scrypt mining software and point it at http://127.0.0.1:9266/
Which is obviously not enough instructions on how and what mining software to use. I tried some scrypt mining programs giving them that ip, user and pass and none of them could see bitmarkd... I am using Nvidea GTX 750 TiCan you give some recomendations on mining software installing and usage, please? And example, maybe?
As it stands only one person can mine this coin, and has done so for at least 1 year, that is why polo has disabled the wallet I spoke to the dev team on slack about sorting it out, they say it needs to get fixed but they are not in any rush to fix it, this was several months ago, i'm not the only one either who has brought this up. I highly suspect it's one of the dev team that is mining the entire supply to them selves, i'm glad that polo has disabled the wallet, at least it stops them from dumping their massive bag on to the market.
thank you for information!
hello
I am new to mining bitmark, and I can't find any full guides how to start mining on Windows. I have already started bitmarkd with config
But I can't find correct Scrypt software to use it with this. And official wiki says only
Can you give some recomendations on mining software installing and usage, please? And example, maybe?
I am new to mining bitmark, and I can't find any full guides how to start mining on Windows. I have already started bitmarkd with config
Code:
rpcuser=...
rpcpassword=...
rpcallowip=192.*.*.* (was 192.168.1.*, didn't work either)
daemon=1
server=1
alertnotify=echo %s
Quote
Launch your preferred scrypt mining software and point it at http://127.0.0.1:9266/
Which is obviously not enough instructions on how and what mining software to use. I tried some scrypt mining programs giving them that ip, user and pass and none of them could see bitmarkd... I am using Nvidea GTX 750 TiCan you give some recomendations on mining software installing and usage, please? And example, maybe?
As it stands only one person can mine this coin, and has done so for at least 1 year, that is why polo has disabled the wallet I spoke to the dev team on slack about sorting it out, they say it needs to get fixed but they are not in any rush to fix it, this was several months ago, i'm not the only one either who has brought this up. I highly suspect it's one of the dev team that is mining the entire supply to them selves, i'm glad that polo has disabled the wallet, at least it stops them from dumping their massive bag on to the market.
hello
I am new to mining bitmark, and I can't find any full guides how to start mining on Windows. I have already started bitmarkd with config
But I can't find correct Scrypt software to use it with this. And official wiki says only
Can you give some recomendations on mining software installing and usage, please? And example, maybe?
I am new to mining bitmark, and I can't find any full guides how to start mining on Windows. I have already started bitmarkd with config
Code:
rpcuser=...
rpcpassword=...
rpcallowip=192.*.*.* (was 192.168.1.*, didn't work either)
daemon=1
server=1
alertnotify=echo %s
Quote
Launch your preferred scrypt mining software and point it at http://127.0.0.1:9266/
Which is obviously not enough instructions on how and what mining software to use. I tried some scrypt mining programs giving them that ip, user and pass and none of them could see bitmarkd... I am using Nvidea GTX 750 TiCan you give some recomendations on mining software installing and usage, please? And example, maybe?
fake or not still holding 60% plus gains
Dev answers:
Quote
We'll be trading on SUPER net soon. But my view is that liaising with polo and other exchanges is the top priority for this month at least, before the next online summit. I dont trade, so it will have to be others that do that drive that. Let's see how far we get. :slightly_smiling_face:
What I think what happened was an accidental transaction got orphaned, and one of the exchanges synced to the wrong chain causing a bit of confusion. But I speculate. It would be great to find out the reason for temp suspend of the wallet. Then maybe we can fix the issue.
I hope wallet suspension is temporary and btm is not delisted. Polo have said that they wont delist us as long as there is active development. I stand ready to volunteer to help develop the coin, if it keeps gonig. Hopefully, there will be more clarity as the month progresses. Then we can so an online summit in June, the next roadmap, technical goals, outreach to new communities and marketing material ...
There is actually a lot of technology for marking already built, so its just a case of getting it (nearer) to production quality.
could have decentralized identity, storage, search, marking and payments all from a desktop client, with lots of very good content, in the next 6 month roadmap. All the pieces are there for that, it's a case of putting it together and making a good user epxerience
What I think what happened was an accidental transaction got orphaned, and one of the exchanges synced to the wrong chain causing a bit of confusion. But I speculate. It would be great to find out the reason for temp suspend of the wallet. Then maybe we can fix the issue.
I hope wallet suspension is temporary and btm is not delisted. Polo have said that they wont delist us as long as there is active development. I stand ready to volunteer to help develop the coin, if it keeps gonig. Hopefully, there will be more clarity as the month progresses. Then we can so an online summit in June, the next roadmap, technical goals, outreach to new communities and marketing material ...
There is actually a lot of technology for marking already built, so its just a case of getting it (nearer) to production quality.
could have decentralized identity, storage, search, marking and payments all from a desktop client, with lots of very good content, in the next 6 month roadmap. All the pieces are there for that, it's a case of putting it together and making a good user epxerience
I read the stuff on the hard fork rules... unanimous (or near it) consent kills any fork, which seemed like a naive thing to even suggest.
Additionally, the thing about the "accidental transaction" and the "wrong chain" has me a bit worried, sounds like a fork or a f-up, which no one is really solving.
The Dev (melvincarvalho) also says he stands ready help develop the coin, if it keeps going, not exactly sounding like he is into it, at the moment.
Then, you think about Bitmark Inc and I start wondering if Bitmark, as we know it, now, is just hoping to ride the coattails of the Chinese project, Bitmark Inc with their funding announcements last year and other news they had.... I checked to see if there was a new wallet on bitmark.io and it is still Bitmark Core 0.9.4.0 beta despite the recent news of releases.... I guess we will see stuff "Soon" since
Quote
There is actually a lot of technology for marking already built, so its just a case of getting it (nearer) to production quality.
could have decentralized identity, storage, search, marking and payments all from a desktop client, with lots of very good content, in the next 6 month roadmap. All the pieces are there for that, it's a case of putting it together and making a good user epxerience
could have decentralized identity, storage, search, marking and payments all from a desktop client, with lots of very good content, in the next 6 month roadmap. All the pieces are there for that, it's a case of putting it together and making a good user epxerience
Blind faith is just as bad as trolling... it would be nice to see some alpha builds for the general public since nearer to production quality seems like they should have that....
I rather think it's the other way around ... the Chinese bitmark.com is riding _our_ coattails.
The hard fork criteria outline proposed by Melvin Carvalho make good sense to me. As long as a majority of the community agree that it is a good think, I don't think it need be 100% unanimous.
The idea of stake being required to create greater returns for staking miner nodes (Master Nodes) is very interesting; I believe this concept was pioneered by Dash.
The concept of Proof-of-Stake to earn "interest", so coins staked for a definite period of time (or number of blocks) earn a certain return is well-liked too. This would change the basic setup of Bitmark as non-inflationary, but if the interest wasn't excessive it should not be a problem. What return on staked coins seems reasonable to you ?
I also like the idea of Proof-of-Stake to enable voting on issues affecting the coin and taking decisions, or setting policy parameters, but all this would have to be elaborated in detail. Do you have more specifics in mind ??
Will be proposing a hard fork to address the issues that have been affecting the bitmark blockchain.
Code for the proposed hard fork is at https://github.com/piratelinux/bitmark on the 0.9.7 branch
A description of the new features and what issues they are addressing is here:
https://github.com/project-bitmark/bitmark/wiki/Hard_Fork_Criteria
~dbKeys
Eta?
what that even mean? I dont see any eta at bitmark hah, mining this wouldnt be worth your time anyway.
the node 60.205.112.102 mines ahead of the group, if the node detects you've found and submitted a block to the rest of the network, it reannounces itself with a higher block count (usually 2 or 3 blocks) and invalidates your chain.
has been happening for years now too, shame, used to be a solid currency.
its still fun sometimes to recompile the -qt version with a few choice lines in rpcmining.cpp commented out, fire it up with -connect=127.0.0.1 so you dont have to be connected to the network to crank out a getblocktemplate; then hit nicehash for a while, then do a manual 'addnode' once you're 100 blocks ahead.
the looks of panic on their faces, priceless.
the node 60.205.112.102 mines ahead of the group, if the node detects you've found and submitted a block to the rest of the network, it reannounces itself with a higher block count (usually 2 or 3 blocks) and invalidates your chain.
Code:
2017-05-24 01:40:22 AddToWallet 32622cd714dfe61e948079d7f5b0f1d236a14246a6981fdd0badc0de2d997ee3 new
2017-05-24 01:40:22 UpdateTip: new best=25fa249302b159e5f18d52e4f150bbd755ef9e1fdde30fd86191fddf64970ad9 height=254204 log2_work=57.257459 tx=876118 date=2017-05-24 01:41:01 progress=1.000001
2017-05-24 01:40:22 AddToWallet 32622cd714dfe61e948079d7f5b0f1d236a14246a6981fdd0badc0de2d997ee3
2017-05-24 01:40:22 ProcessBlock: ACCEPTED
2017-05-24 01:40:22 CreateNewBlock(): total size 1000
2017-05-24 01:42:22 ProcessBlock: ORPHAN BLOCK 0, prev=6dbf303c7b21b78c7a99fdd88e138e161cd5c1a8eeb0bfb8caa1ffcd97b4dbd4
2017-05-24 01:42:23 ProcessBlock: ACCEPTED
2017-05-24 01:42:24 ProcessBlock: ACCEPTED
2017-05-24 01:42:24 ProcessBlock: ACCEPTED
2017-05-24 01:42:24 UpdateTip: new best=d1151e9ec46df130319a0f2dd71b10237514cdb05767b576c762ab473c394798 height=254203 log2_work=57.257458 tx=876117 date=2017-05-24 01:40:51 progress=0.999997
2017-05-24 01:42:24 AddToWallet 32622cd714dfe61e948079d7f5b0f1d236a14246a6981fdd0badc0de2d997ee3
2017-05-24 01:42:24 UpdateTip: new best=d79fe275df2a4df729cfb22a3a874ca0b8ee3973a2f7c75cda7a3c22e3f70653 height=254202 log2_work=57.257457 tx=876116 date=2017-05-24 01:40:40 progress=0.999996
2017-05-24 01:42:24 AddToWallet 1b537e4e6e3a71d60a12a228100f2061e4d3c879134646b72264710c83d8e2f2
2017-05-24 01:42:24 UpdateTip: new best=80590c77805804486214b1fdfdc3c1962ab408e45d77287d69ea68c8e13b2e07 height=254201 log2_work=57.257456 tx=876115 date=2017-05-24 01:39:43 progress=0.999994
2017-05-24 01:42:24 AddToWallet ff03caa8211524500eabf165a259eea4d38a701e9390329c3c3b7b268822391f
2017-05-24 01:42:24 UpdateTip: new best=875a0f55cce896c12b2c590d32ef8d6fd2290eccc5704b6030151d6177774ac1 height=254200 log2_work=57.257455 tx=876114 date=2017-05-24 01:35:41 progress=0.999986
2017-05-24 01:42:24 AddToWallet c5762fa37ba94e1486c0da15ca40d36e8cd6f4ca0eb72b538d5cb062f48f5688
2017-05-24 01:42:24 UpdateTip: new best=a2e7db8af31ed5e3d76b463496550468b757c01a79087451d6df4942d340c3eb height=254201 log2_work=57.257456 tx=876115 date=2017-05-24 01:36:55 progress=0.999988
2017-05-24 01:42:24 UpdateTip: new best=841dc30447594025d9abd270dbc0f093d4645adb85f94f37d61361a40db66dea height=254202 log2_work=57.257457 tx=876116 date=2017-05-24 01:41:20 progress=0.999998
2017-05-24 01:42:24 UpdateTip: new best=157bc8b41f40325a3e1adf38d7faf30b53e2fd17eb97ef6b855ba524c5dee1ee height=254203 log2_work=57.257458 tx=876117 date=2017-05-24 01:42:08 progress=0.999999
2017-05-24 01:42:24 UpdateTip: new best=6dbf303c7b21b78c7a99fdd88e138e161cd5c1a8eeb0bfb8caa1ffcd97b4dbd4 height=254204 log2_work=57.257459 tx=876118 date=2017-05-24 01:42:36 progress=1.000000
2017-05-24 01:42:25 UpdateTip: new best=833c3747c3ae92f61bf44d9c067e96f915169b59c1ac4d3ec55ff42ad5c3b004 height=254205 log2_work=57.257461 tx=876119 date=2017-05-24 01:42:41 progress=1.000001
has been happening for years now too, shame, used to be a solid currency.
its still fun sometimes to recompile the -qt version with a few choice lines in rpcmining.cpp commented out, fire it up with -connect=127.0.0.1 so you dont have to be connected to the network to crank out a getblocktemplate; then hit nicehash for a while, then do a manual 'addnode' once you're 100 blocks ahead.
the looks of panic on their faces, priceless.
ROTFL, this made my day. LOL
Where the devs at?
Jump to: