Topic: [ANN] Datacoin - Censorship-Free Data Storage - page 68. (Read 66642 times)
Recently,pretty much project required you to hold coins long term since they usually don't have working platforms to show in the beginning.
just released Apertus v0.3.12-beta.
you can download it from http://apertus.io or directly from github at https://github.com/HugPuddle/Apertus/releases
RELEASE NOTES:
Feature: Drop down list to select amount of search results
Feature: Persist Monitor settings and start automatically on load
Fix: implementing gettransaction instead of getrawtransaction in datacoin native support was preventing stored items from being viewed in a remote wallet.
you can download it from http://apertus.io or directly from github at https://github.com/HugPuddle/Apertus/releases
RELEASE NOTES:
Feature: Drop down list to select amount of search results
Feature: Persist Monitor settings and start automatically on load
Fix: implementing gettransaction instead of getrawtransaction in datacoin native support was preventing stored items from being viewed in a remote wallet.
[APERTUS UPDATE]
Good news! HugPuddle.org is currently testing a fix for the bug that was preventing it from rebuilding variable storage etchings stored in a remote wallet.
We will be testing it's functionality soon by archiving a message in a wallet located in Moorhead MN and rebuilding the message via transaction ID in a remote wallet located in Long Beach CA. if it works as expected we will release the fix in v0.3.12-beta and make it available for download at Apertus.io shortly.
PS: If you are experimenting with DTC-V (Datacoin Variable Storage) you may begin to see your etchings show up on the bitfossil.org real time indexer later in the evening as we deploy the fix.
Thanks for your time.
Good news! HugPuddle.org is currently testing a fix for the bug that was preventing it from rebuilding variable storage etchings stored in a remote wallet.
We will be testing it's functionality soon by archiving a message in a wallet located in Moorhead MN and rebuilding the message via transaction ID in a remote wallet located in Long Beach CA. if it works as expected we will release the fix in v0.3.12-beta and make it available for download at Apertus.io shortly.
PS: If you are experimenting with DTC-V (Datacoin Variable Storage) you may begin to see your etchings show up on the bitfossil.org real time indexer later in the evening as we deploy the fix.
Thanks for your time.
Hi Team,
Tests successful:
"One small step for a block... one giant leap for blockchain"
http://bitfossil.org/8587d9f36e8d62202147921a8f0039a9bbcdd75abc11d2b797cf4ce307e8397c/index.htm
"Datacoin native field etch test on a non HugPuddle network machine to see if a HugPuddle networked machine pics up the Datacoin native field etching"
http://bitfossil.org/2a9e4d8c76a5fed92e3f9c6de7aec98a273751cb9c0dd6b71d385cbe3cd9bd38/index.htm
Native Datacoin variable field in full usage by Apertus, and completely viewable on bitFossil.org
Onwards and upwards.
The AtomSea
Lovely, lovely. One problem sorted out thanks to Veronium and your goodselves.
I must say I am very excited about the Twitter/Snapchat clones you have on testnet. I know Graham and Chicago will have the importaddress RPC call sorted out.
-extro
Maybe if we omit any of the src/qt{/*.cpp, /*.h} changes and just shunt it into the RPC core?
That might work but I have a nasty suspicion that watch-address txs will still turn up in the GUI unless explicitly filtered out. It did actually work for Slimcoin but I absent-mindedly imported Slimcoin's burn address and that promptly brought the client to a standstill while it futilely calculated the staking weight of 000s of txs for which it didn't have a privkey, sigh. There was an earlier PR (https://github.com/bitcoin/bitcoin/pull/2861) for the same feature, I found the discussion quite illuminating - the inclusion of pubkey-only addresses also has implications for a buncha other RPC commands and whilst the current focus is on Apertus' specialised and limited use case, in other broader use-case contexts, consequences for users need to be understood in detail - such as importing an address (pubkey) and subsequently, at a later date, importing the corresponding privkey and then (not unreasonably) expecting to be able to spend from what was previously a watch-only address but is now expected to be an “ordinary” address.
Cheers
Graham
There were some GUI infelicities which do seem to have been addressed in this commit for Dogecoin (Core 0.9, I think) - https://github.com/dogecoin/dogecoin/commit/5ca5fb179e3ac873c9fe547b6bac68bdab87c0c7
Hi Graham,
It didn't go so well on my first pass either.
Maybe if we omit any of the src/qt{/*.cpp, /*.h} changes and just shunt it into the RPC core?
It got derailed from an easy integration while looking at the src/qt/walletmodel.cpp changes and ours has no WalletModel::getOutputs to patch.
Best Regards,
-Chicago
Additionally, here is a reference to the original watch-only-addresses commit in Bitcoin Core.
A backport to Slimcoin didn't work so well - imported addresses not excluded from staking calcs, more work required. That shouldn't be an issue for Datacoin, though. There were some GUI infelicities which do seem to have been addressed in this commit for Dogecoin (Core 0.9, I think) - https://github.com/dogecoin/dogecoin/commit/5ca5fb179e3ac873c9fe547b6bac68bdab87c0c7
Cheers
Graham
Team, I just noticed a limitation with datacoin and Apertus.io. the version I am using v0.1.2.0dtc-hp11-unk-beta does not support the importaddress RPC call that was introduced with bitcoin 0.10.x
This is critical. Currently we are testing Datacoin 0.8.6 and will upgrade to 0.10.x in time.Hello,
Additionally, here is a reference to the original watch-only-addresses commit in Bitcoin Core.
Best Regards,
-Chicago
[APERTUS UPDATE]
Good news! HugPuddle.org is currently testing a fix for the bug that was preventing it from rebuilding variable storage etchings stored in a remote wallet.
We will be testing it's functionality soon by archiving a message in a wallet located in Moorhead MN and rebuilding the message via transaction ID in a remote wallet located in Long Beach CA. if it works as expected we will release the fix in v0.3.12-beta and make it available for download at Apertus.io shortly.
PS: If you are experimenting with DTC-V (Datacoin Variable Storage) you may begin to see your etchings show up on the bitfossil.org real time indexer later in the evening as we deploy the fix.
Thanks for your time.
Good news! HugPuddle.org is currently testing a fix for the bug that was preventing it from rebuilding variable storage etchings stored in a remote wallet.
We will be testing it's functionality soon by archiving a message in a wallet located in Moorhead MN and rebuilding the message via transaction ID in a remote wallet located in Long Beach CA. if it works as expected we will release the fix in v0.3.12-beta and make it available for download at Apertus.io shortly.
PS: If you are experimenting with DTC-V (Datacoin Variable Storage) you may begin to see your etchings show up on the bitfossil.org real time indexer later in the evening as we deploy the fix.
Thanks for your time.
Hi Team,
Tests successful:
"One small step for a block... one giant leap for blockchain"
http://bitfossil.org/8587d9f36e8d62202147921a8f0039a9bbcdd75abc11d2b797cf4ce307e8397c/index.htm
"Datacoin native field etch test on a non HugPuddle network machine to see if a HugPuddle networked machine pics up the Datacoin native field etching"
http://bitfossil.org/2a9e4d8c76a5fed92e3f9c6de7aec98a273751cb9c0dd6b71d385cbe3cd9bd38/index.htm
Native Datacoin variable field in full usage by Apertus, and completely viewable on bitFossil.org
Onwards and upwards.
The AtomSea
[APERTUS UPDATE]
Good news! HugPuddle.org is currently testing a fix for the bug that was preventing it from rebuilding variable storage etchings stored in a remote wallet.
We will be testing it's functionality soon by archiving a message in a wallet located in Moorhead MN and rebuilding the message via transaction ID in a remote wallet located in Long Beach CA. if it works as expected we will release the fix in v0.3.12-beta and make it available for download at Apertus.io shortly.
PS: If you are experimenting with DTC-V (Datacoin Variable Storage) you may begin to see your etchings show up on the bitfossil.org real time indexer later in the evening as we deploy the fix.
Thanks for your time.
Good news! HugPuddle.org is currently testing a fix for the bug that was preventing it from rebuilding variable storage etchings stored in a remote wallet.
We will be testing it's functionality soon by archiving a message in a wallet located in Moorhead MN and rebuilding the message via transaction ID in a remote wallet located in Long Beach CA. if it works as expected we will release the fix in v0.3.12-beta and make it available for download at Apertus.io shortly.
PS: If you are experimenting with DTC-V (Datacoin Variable Storage) you may begin to see your etchings show up on the bitfossil.org real time indexer later in the evening as we deploy the fix.
Thanks for your time.
What's the most active branch/fork of the DTC repo?
Chicago's branch is the furthest in terms of development. https://github.com/CoiningPress/datacoin
Currently for testing as Datacoin 0.8.6.
Wow those are some clean commits, me gusta.
Team, I just noticed a limitation with datacoin and Apertus.io. the version I am using v0.1.2.0dtc-hp11-unk-beta does not support the importaddress RPC call that was introduced with bitcoin 0.10.x
This is critical. Currently we are testing Datacoin 0.8.6 and will upgrade to 0.10.x in time.There is a backport to 0.8.6 which might ease things in the interim: https://github.com/litecoin-project/bitcoinomg/commit/a946dcdb2a1db076e974fe58bed6a47d97000b1f
Cheers
Graham
What's the most active branch/fork of the DTC repo?
Chicago's branch is the furthest in terms of development. https://github.com/CoiningPress/datacoin
Currently for testing as Datacoin 0.8.6.
Graham's branch is the reference client. https://github.com/gjhiggins/datacoin
What's the most active branch/fork of the DTC repo?
Team, I just noticed a limitation with datacoin and Apertus.io. the version I am using v0.1.2.0dtc-hp11-unk-beta does not support the importaddress RPC call that was introduced with bitcoin 0.10.x because of this datacoin will not support several of the Apertus.io social media like functions that other blockchains are able to use.
the importaddress call is used to implement hash tag keywords, Proof of ownership searching, following profiles and decentralized voting. none of these features will work properly on datacoin unless the importaddress RPC call is implemented. my previous comments about starting a #rDatacoin thread on datacoin is not possible at this time. you can still use the #rDatacoin keyword and other keywords in your etching but nobody will be able to search for them unless importaddress() is supported.
Thanks for your time.
embii
the importaddress call is used to implement hash tag keywords, Proof of ownership searching, following profiles and decentralized voting. none of these features will work properly on datacoin unless the importaddress RPC call is implemented. my previous comments about starting a #rDatacoin thread on datacoin is not possible at this time. you can still use the #rDatacoin keyword and other keywords in your etching but nobody will be able to search for them unless importaddress() is supported.
Thanks for your time.
embii
This is critical. Currently we are testing Datacoin 0.8.6 and will upgrade to 0.10.x in time.
-extro
it will be great if there are more exchanges for dtc
Datacoin was approved to be listed on HitBTC, it was frightfully expensive so we didn't proceed
We are on a maby list at Kraken
There is currently an application in with Bit-Z
Recently I have sent out applications to a few Japanese/Korean exchanges, not expecting a reply back for awhile
considering how busy they are with influx of new users.
Active development will get Datacoin on the exchanges, sure you can buy your way in but it's only a matter of time before
your coin is on that delisting/low volume notice.
it will be great if there are more exchanges for dtc
Team, I just noticed a limitation with datacoin and Apertus.io. the version I am using v0.1.2.0dtc-hp11-unk-beta does not support the importaddress RPC call that was introduced with bitcoin 0.10.x because of this datacoin will not support several of the Apertus.io social media like functions that other blockchains are able to use.
the importaddress call is used to implement hash tag keywords, Proof of ownership searching, following profiles and decentralized voting. none of these features will work properly on datacoin unless the importaddress RPC call is implemented. my previous comments about starting a #rDatacoin thread on datacoin is not possible at this time. you can still use the #rDatacoin keyword and other keywords in your etching but nobody will be able to search for them unless importaddress() is supported.
Thanks for your time.
embii
the importaddress call is used to implement hash tag keywords, Proof of ownership searching, following profiles and decentralized voting. none of these features will work properly on datacoin unless the importaddress RPC call is implemented. my previous comments about starting a #rDatacoin thread on datacoin is not possible at this time. you can still use the #rDatacoin keyword and other keywords in your etching but nobody will be able to search for them unless importaddress() is supported.
Thanks for your time.
embii
Am I seeing blocks that are substantially under 60 seconds here (contrary to what we advertise) ?
That perception is reinforced by what I'm seeing on the Datacoin ACME: http://tessier.bel-epa.com:5059 (select Blocks->Browse the recent blockchain to see intervals for the last 100 blocks)
(Apologies for the unconscionable length of time it's taking me to get round to polishing up/finishing off the Datacoin ACME. Once again, I've taken on far too much and am having to plough through it.)
Cheers
Graham
Hi Team,
Am I seeing blocks that are substantially under 60 seconds here (contrary to what we advertise) ?
(image from http://www.bitFossil.org -- specifically this etching -- http://www.bitfossil.org/ab6d565b4870cf08e7eeca820567dbd85967352eafb16ade1d440fe462947985/index.htm -- screen capture from https://dtc.graymines.net)
Let me know!
Kind Regards,
AtomSea
Am I seeing blocks that are substantially under 60 seconds here (contrary to what we advertise) ?
(image from http://www.bitFossil.org -- specifically this etching -- http://www.bitfossil.org/ab6d565b4870cf08e7eeca820567dbd85967352eafb16ade1d440fe462947985/index.htm -- screen capture from https://dtc.graymines.net)
Let me know!
Kind Regards,
AtomSea
BTW, on pool times are timestamps when share/block were saved into DB, that can be different from exact block time.
i etched the first #rDatacoin post on datacoin production net last night detailing the substantial cost savings obtained by using DTC-V instead of DTC. unfortunately the post is on DTC-V and there is an Apertus bug preventing external wallets from rebuilding it. we hope to have this bug resolved shortly. Until then we have pushed the etching out onto bitfossil so it can be read by others. here is the forum post.
http://bitfossil.com/e02dbd6c1b95b4eb84aac6bf1ec7a1bae6c537d80f53aeadbe676c47f462678f/index.htm
consider adding your voice to the thread by using the case sensitive #rDatacoin keyword in your etchings. consider using the datacoin testnet for discussions that do not need to persist.
Here is a video explaining some of the social media features that Apertus.io enables on most blockchains.
https://youtu.be/ItYf4G1yPYo
thanks for your time
http://bitfossil.com/e02dbd6c1b95b4eb84aac6bf1ec7a1bae6c537d80f53aeadbe676c47f462678f/index.htm
consider adding your voice to the thread by using the case sensitive #rDatacoin keyword in your etchings. consider using the datacoin testnet for discussions that do not need to persist.
Here is a video explaining some of the social media features that Apertus.io enables on most blockchains.
https://youtu.be/ItYf4G1yPYo
thanks for your time
Jump to: