Even if you will do chmod a+x on leveldb/build_detect_platform you still can't compile wallet.
I don't seem to be able to reproduce that problem. When build_detect_platform is -x then “make clean && make” succeeds. Could you post the error messages? Cheers Graham |
|
|
|
That is actually criminal and it does not sound like Mr. Spread at all
I'm unsure about whether the term “criminal” can be accurate in the context of a commons which is under no specific legal jurisdiction but I agree with your point about it not sounding like Mr. Spread at all. Mr. Spread comes over as rather a private person with well-considered views (as do all the programmers of his calibre with whom I am acquainted) but you can catch glimpses of his personality here'n'there and it does tend to back up your point - e.g. Mr. Spread's innovative take on the value bound to pszTimestamp, a variable described thusly in a 2013 bct thread: The phrase is hashed into the block. It is meant to be a proof of date. It is meant to be some fact that would not have been known before the date in it, to prove the block was made on of after that date.
A typical example is provided in an earlier post to that thread: “ NY Times 05/Oct/2011 Steve Jobs, Apple’s Visionary, Dies at 56”. earlz's code reviews usually include an assessment of how well the coin's pszTimestamp value serves the proof-of-date purpose, f'rinstance his review of darktoken is annotated: Problems: * MODERATE: genesis seed is not a news event. The value of Spreadcoin's pszTimestamp: “Bitcoin block #312971 ~1cbec6ee63d173ea4b2c645cdb162aae6637170ecbb43c15” Which is rather elegant when you think about it. My take on it is: if you want to get to know Mr. Spread better, read his code. Cheers Graham |
|
|
|
-We are at a standstill with regard to development.
Kinda. The repos has a stealth transaction development branch: https://github.com/Deepcoinbiz/Deepcoin/commits/new-sx-0.8.7. The work is basically complete except for a few compilation errors arising from inconsistent types migrated in along with the donor code. https://github.com/gjhiggins/Deepcoin/commits/new-sx-0.8.7 is where I fudged them to get a compilation and added a Travis CI config file ( build results) but have yet to double-check that the actual program semantics are being properly respected (uint64 vs uint64_t, mainly). Might be worth setting up a testnet node, run some tests of the branch code. Cheers Graham |
|
|
|
Must be some error in code, i searched but couldn't find anything.
 The stake reward appears to be 100000000 times too high. https://github.com/gjhiggins/dreamcoin/blob/master/src/main.cpp#L1005 <- Dreamcoinint64_t nSubsidy = nCoinAge * nRewardCoinYear / 365 / COIN;vs: https://github.com/gascrypto/Gascoin/blob/master/src/main.cpp#L1020 <- Gascoinint64_t nSubsidy = nCoinAge * nRewardCoinYear / 365;(Gascoin shares its code with Dreamcoin) Dreamcoin// miner's coin stake reward based on coin age spent (coin-days)
int64_t GetProofOfStakeReward(int64_t nCoinAge, int64_t nFees)
{
int64_t nRewardCoinYear;
nRewardCoinYear = MAX_MINT_PROOF_OF_STAKE;
int64_t nSubsidy = nCoinAge * nRewardCoinYear / 365 / COIN;
if (fDebug && GetBoolArg("-printcreation"))
printf("GetProofOfStakeReward(): create=%s nCoinAge=%"PRId64"\n",
FormatMoney(nSubsidy).c_str(), nCoinAge);
return nSubsidy + nFees;
}
// miner's coin stake reward based on coin age spent (coin-days)
int64_t GetProofOfStakeReward(int64_t nCoinAge, int64_t nFees)
{
int64_t nRewardCoinYear;
nRewardCoinYear = COIN_YEAR_REWARD;
int64_t nSubsidy = nCoinAge * nRewardCoinYear / 365;
if (fDebug && GetBoolArg("-printcreation"))
printf("GetProofOfStakeReward(): create=%s nCoinAge=%"PRId64"\n",
FormatMoney(nSubsidy).c_str(), nCoinAge);
return nSubsidy;
}
where: static const int64_t MAX_MINT_PROOF_OF_STAKE = 0.15 * COIN; // 15% annual interest <- Dreamcoinand static const int64_t COIN_YEAR_REWARD = 20 * CENT; // 20% annual interest <- Gascoinrespectively. For convenience here's the arithmetic, expressed in Python with an arbitrary value of 30 for nCoinAge: >>> 30 * (0.15 * 100000000) / 365 / 100000000 # Dreamcoin 15%
0.012328767123287671
>>> 30 * (20 * 1000000) / 365 # Gascoin 20%
1643835.6164383562
>>> 30 * (0.20 * 100000000) / 365 / 100000000 # Dreamcoin if it were 20%
0.016438356164383564
>>> 1643835.6164383562 / 0.016438356164383564 # The difference as a ratio
99999999.99999999
Seems to explain the symptoms. Anyone concur? Cheers Graham |
|
|
|
After the wallet has synched and Abe has read in the full blockchain (which will take most of the day), I'll make the block explorer publicly accessible.
In the event, reading the blockchain into postgresql took most of the day and night: https://minkiz.co/abe/chain/BeeCoin2ChainIt's a proof-of-concept demonstrator temporarily hosted on our server pending adoption by the Beecoin community. Cheers Graham |
|
|
|
We have an infographic - it's rough and ready and only covers the top 40 for 2014 but it might give you another perspective:  https://minkiz.co/coin/infographics/cCheers Graham Edit: added screenshot |
|
|
|
Sifcoin has just a chain of hashes while quark has branches.
To the Russian team's credit, the chained-hash tactic was introduced solely in the hope of delaying the onset of ASIC mining and not as some imagined enhancement to security. Quarkcoin is still breezily touting their particular folklore combiner as a security enhancement. Cheers Graham |
|
|
|
Ach, I got myself trapped in a twisty little maze of redirects* New transient URL for Sifcoin Abe explorer: https://minkiz.co/abe/chain/SiFcoinCheers Graham * or was it a little twisty maze of redirects? |
|
|
|
It's absolutely amazing all the hostility between communities in such a small niche. It really doesn't benefit anyone whatsoever.
I believe you're quite mistaken in your perception of hostility between communities. Community sentiment is in no way reflected in the actions of a handful of semi-pro trolls paid to conduct a disruptive smear campaign. Only the trolls diss DRK, spreaders don't 'cos Mr Spread don't and that's the way it is. Cheers Graham |
|
|
|
DEAD COIN ,dev has gone.  Awww, are you lost, my little troll? The Spreadcoin thread is thisaway -> Cheers Graham |
|
|
|
There is a problem with new BEE sources that you gave me. And I can understand why Mark from Allcoin can't compile it.
I reckon it's just the usual issue of src/leveldb/build_detect_platform not having the 'x' flag set: Building LevelDB ...
/bin/sh: 1: ./build_detect_platform: Permission denied
make[1]: Entering directory `/www/lib/abe/beecoinv2/beecoinv2exchange/src/leveldb'
Makefile:18: build_config.mk: No such file or directory
make[1]: *** No rule to make target `build_config.mk'. Stop.
make[1]: Leaving directory `/www/lib/abe/beecoinv2/beecoinv2exchange/src/leveldb'
which is fixable with: $ chmod a+x leveldb/build_detect_platform
e.g. gjh@chrome:/www/lib/abe/beecoinv2/beecoinv2exchange/src$ chmod a+x leveldb/build_detect_platform
gjh@chrome:/www/lib/abe/beecoinv2/beecoinv2exchange/src$ make -f makefile.unix
/bin/sh ../share/genbuild.sh obj/build.h
fatal: Not a git repository (or any of the parent directories): .git
Building LevelDB ...
make[1]: Entering directory `/www/lib/abe/beecoinv2/beecoinv2exchange/src/leveldb'
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c db/builder.cc -o db/builder.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c db/c.cc -o db/c.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c db/dbformat.cc -o db/dbformat.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c db/db_impl.cc -o db/db_impl.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c db/db_iter.cc -o db/db_iter.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c db/filename.cc -o db/filename.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c db/log_reader.cc -o db/log_reader.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c db/log_writer.cc -o db/log_writer.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c db/memtable.cc -o db/memtable.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c db/repair.cc -o db/repair.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c db/table_cache.cc -o db/table_cache.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c db/version_edit.cc -o db/version_edit.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c db/version_set.cc -o db/version_set.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c db/write_batch.cc -o db/write_batch.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c table/builder.cc -o table/builder.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c table/block.cc -o table/block.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c table/block.cc -o table/block.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c table/format.cc -o table/format.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c table/iterator.cc -o table/iterator.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c table/merger.cc -o table/merger.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c table/builder.cc -o table/builder.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c table/table.cc -o table/table.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c table/iterator.cc -o table/iterator.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c util/arena.cc -o util/arena.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c util/bloom.cc -o util/bloom.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c util/cache.cc -o util/cache.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c util/coding.cc -o util/coding.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c util/comparator.cc -o util/comparator.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c util/crc32c.cc -o util/crc32c.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c util/env.cc -o util/env.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c util/env_posix.cc -o util/env_posix.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c util/env_win.cc -o util/env_win.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c util/filter_policy.cc -o util/filter_policy.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c util/hash.cc -o util/hash.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c util/histogram.cc -o util/histogram.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c util/logging.cc -o util/logging.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c util/options.cc -o util/options.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c util/status.cc -o util/status.o
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG -c port/port_posix.cc -o port/port_posix.o
rm -f libleveldb.a
ar -rs libleveldb.a db/builder.o db/c.o db/dbformat.o db/db_impl.o db/db_iter.o db/filename.o db/log_reader.o db/log_writer.o
db/memtable.o db/repair.o db/table_cache.o db/version_edit.o db/version_set.o db/write_batch.o table/block_builder.o
table/block.o table/filter_block.o table/format.o table/iterator.o table/merger.o table/table_builder.o table/table.o
table/two_level_iterator.o util/arena.o util/bloom.o util/cache.o util/coding.o util/comparator.o util/crc32c.o util/env.o
util/env_posix.o util/env_win.o util/filter_policy.o util/hash.o util/histogram.o util/logging.o util/options.o util/status.o
port/port_posix.o
ar: creating libleveldb.a
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -DNDEBUG
-c helpers/memenv/memenv.cc -o helpers/memenv/memenv.o
rm -f libmemenv.a
ar -rs libmemenv.a helpers/memenv/memenv.o
ar: creating libmemenv.a
make[1]: Leaving directory `/www/lib/abe/beecoinv2/beecoinv2exchange/src/leveldb'
g++ -c -O2 -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -g
-DBOOST_SPIRIT_THREADSAFE -I/www/lib/abe/beecoinv2/beecoinv2exchange/src -I/www/lib/abe/beecoinv2/beecoinv2exchange/src/obj
-DUSE_IPV6=1 -I/www/lib/abe/beecoinv2/beecoinv2exchange/src/leveldb/include -I/www/lib/abe/beecoinv2/beecoinv2exchange/src/leveldb/helpers
-DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2
-MMD -MF obj/txdb-leveldb.d -o obj/txdb-leveldb.o txdb-leveldb.cpp
g++ -O2 -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE
-I/www/lib/abe/beecoinv2/beecoinv2exchange/src -I/www/lib/abe/beecoinv2/beecoinv2exchange/src/obj -DUSE_IPV6=1
-I/www/lib/abe/beecoinv2/beecoinv2exchange/src/leveldb/include -I/www/lib/abe/beecoinv2/beecoinv2exchange/src/leveldb/helpers
-DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2
-o beecoinv2d obj/alert.o obj/version.o obj/checkpoints.o obj/netbase.o obj/addrman.o obj/crypter.o obj/key.o obj/db.o
obj/init.o obj/irc.o obj/keystore.o obj/miner.o obj/main.o obj/net.o obj/protocol.o obj/bitcoinrpc.o obj/rpcdump.o obj/rpcnet.o
obj/rpcmining.o obj/rpcwallet.o obj/rpcblockchain.o obj/rpcrawtransaction.o obj/script.o obj/sync.o obj/util.o obj/wallet.o
obj/walletdb.o obj/noui.o obj/kernel.o obj/pbkdf2.o obj/scrypt.o obj/scrypt-arm.o obj/scrypt-x86.o obj/scrypt-x86_64.o
obj/groestl.o obj/blake.o obj/bmw.o obj/skein.o obj/keccak.o obj/shavite.o obj/jh.o obj/luffa.o obj/cubehash.o obj/echo.o
obj/simd.o obj/txdb-leveldb.o -Wl,-z,relro -Wl,-z,now -Wl,-Bdynamic -l boost_system -l boost_filesystem -l boost_program_options
-l boost_thread -l db_cxx -l ssl -l crypto -Wl,-Bdynamic -l z -l dl -l pthread
/www/lib/abe/beecoinv2/beecoinv2exchange/src/leveldb/libleveldb.a
/www/lib/abe/beecoinv2/beecoinv2exchange/src/leveldb/libmemenv.a
gjh@chrome:/www/lib/abe/beecoinv2/beecoinv2exchange/src$
Cheers Graham Added linebreak for display sanity |
|
|
|
Is this good software to use as a bitcoin block explorer on a web server that will get a moderate amount of traffic, or is it too slow/bulky?
What's your definition of “moderate traffic”? What are you anticipating in terms of page views per second? Cheers Graham |
|
|
|
If that doesn't work, try adding the addnodes to the conf specified above by gjhigginis (thank you btw) and restart your wallet.
np (I'm seeing a fairly steady trickle which is mounting up and I'm beginning to feel obliged)  Cheers Graham |
|
|
|
I agree that the article should be much more explained. Your points help me to recognize where I need to put more emphasis.
The mathematico-logical background needs expanding some and needs to be a bit more coherent about the solidity it confers to the principles of what you're aiming to do with rules. The section on RDF is a bit loose but that may be just a linguistic challenge (you describe the components of a triple/quad as “words”, which they certainly aren't). As for the various references to ontology/ontologies, I can't help but think we're working to two entirely different definitions because, try as I might, I just can't seem to build an understanding that leads me to the same conclusions as you. I'm tempted wave my hands vigorously and refer you to the extensive body of research into just how mind-numbingly difficult it is to combine or even cross-correlate ontologies but that would be mischievous now that you've accepted my critique  I'll limit myself to suggesting that you double-check your assumptions about the feasibility of freely combining user-developed ontologies because my understanding is that the field remains very much at the research stage. I'm passingly familiar with EulerGUI and I'm somewhat surprised at your choice (as opposed to Protege, by contrast). It is (unfortunately) ill-resourced and has fallen behind the curve. I note that they claim to support FuXi, which is going back about five years now. Chime has no current plan to take Fuxi forward and so it is now sadly confined to either the ‘layercake’ frozen Python 2.6/RDFLib 2.4.1 package or my now-obsolete port for use with RDFLib>=3 (pre SPARQL 1.1). FuXi doesn't work with gromgull's SPARQL 1.1 implementation and isn't likely to without a major refactoring that Chime has no intention of doing, aiui. So, for any forward-looking project, FuXI isn't really a viable option. I won't comment on cwm's functionality. aiui, it remains timbl's personal code sandpit and I'm not even sure it's officially maintained. I believe it's not compatible with Python 3 which is not necessarily a show-stopper in itself but that must blight its candidacy as underpinning reasoning technology for any ambitious new project, just in terms of executing in anything less than a geological timescale. I severely doubt that everyday users will be comfortable using Attempto --- I'm fairly sure that successful use requires users to undergo a significant amount of training. You're correct in that it's the only game in town but whilst that might be adequate for research purposes, I question whether it's suitable for imminent deployment - if you can't find at least a handful of successful real-world deployments, I suggest your reconsider the whole NL aspects of the tauchain project with an emphasis on checking what's currently actually feasible and not just researchers' fond imaginings. On the NL side, I did explore Quepy's NL features in relation to a semweb project that I'm currently pursuing. The project's domain of discourse is the re-presentation of transparency information otherwise ineptly published by the UK Parliament (c.f. owl-o-parl.org) and the Quepy exploration was oriented thus. I published a write-up of my Quepy investigation which I shall hesitantly recommend to other readers of this thread in that they might find it accessible and gain some illumination on RDF, etc. Cheers Graham |
|
|
|
A pointer to a wikipedia entry doesn't provide adequate support for your statement. The fact that you think it does means that our discussion is already at cross-purposes. Throughout the document, you continually refer readers in a vague fashion to intellectually demanding areas of mathematics and logic as though you expect them to be able to work out for themselves the verification of your claims. It is incumbent on you, the solicitor of investment funding, to provide a comprehensible explanation of how the work in these domains explicitly supports your approach, mere hand-waving references just won't do. Cheers Graham |
|
|
|
I'll be glad for a feedback about unclear points from the paper. Yes, it is hard to explain, and I'm looking for the words to make it clearer. I'll therefore be very thankful for specific questions.
Well, I get where you're planning to go but i) the rationale is somewhat trivially showy and you seem to have both ii) seriously overestimated the capabilities of the current technology and iii) seriously underestimated the scope and scale of the challenge (to a degree that forces me to question the depth of your understanding of the domain). i) You need to provide more support for breathtakingly-wide statements such as “This class is isomorphic to the class of intuitionistic proofs.” (Can you prove it?) ii) Let's take Déductions as an example, what is actually available is: “... rules in N3 language to generate simple Create-Update applications for Java Swing platform from OWL, RDFS, or UML ...” That's parsecs away from the capability that you're assuming will be available to underpin your modelling. iii) The complexity of the modelling task militates against anything less powerful than OWL Full and that effectively renders the task impracticable with contemporary reasoners. And - you'll find out for yourself soon enough when you get down the nitty-gritty - all this nonsense about bolting ontologies together is just that. BTW, you should probably include in the references Jezza Carroll and Chris Bizer's original paper: Modelling Context using Named Graphs. (And you should note that adopting this tactic for modelling context then obliges you to introduce and maintain an explicit temporal representation (of “now”) which is going to pose its own profound problems for the reasoning). I will say that your approach is at least broadly coherent, as opposed to merely spouting risible gobbledygook like the other altcoins that purport to wave an AI flag. $2m won't cover it though, $20m just might. Cheers Graham |
|
|
|
I was having syncing issues as well. I added these to the securitycoin.conf file
addnode=...
Does not work for me... Try these, straight from getpeerinfo: addnode=31.17.30.35:59842 addnode=31.17.30.35:62381 addnode=37.187.244.54:15793 addnode=37.201.240.189:53021 addnode=37.201.240.189:53198 addnode=37.59.21.58:15793 addnode=46.165.209.144:15793 addnode=50.195.111.54:60919 addnode=68.96.191.5:54510 addnode=71.29.186.250:62465 addnode=71.29.186.250:63626 addnode=80.56.218.2:15793 addnode=81.249.158.76:15793 addnode=82.239.75.242:15793 addnode=92.222.181.200:15793 addnode=93.143.90.37:59725 addnode=95.96.100.100:58897 addnode=138.91.64.21:1024 addnode=167.114.114.186:15793 addnode=176.184.17.43:15793 addnode=192.99.21.103:49010 addnode=206.132.52.29:61479 addnode=206.132.52.29:61787 Cheers Graham |
|
|
|
It's gross revenue in general ...
Este, thanks for the clarification. Much appreciated. Cheers Graham |
|
|
|
I'm unable to sync wallet for last few days, is anyone facing anything similar ?
I know it's not much consolation but the wallet appears to be working okay for me. Details, in case it helps:  It frequently receives “unaccepted” amounts that never get confirmed, as shown in the screenshot. Doesn't seem to affect the overall functioning AFAICT. Cheers Graham |
|
|
|
SuperNET is based around the idea of alts combining resources and working together towards a greater goal. Each currency is unique though so it's not quite the same as your proposed idea of similar coins working together, but similar in spirit.
I've made a few attempts to “get” SuperNET but I find the description too vague and hand-wavy to be able to build a satisfactory understanding. For instance, pertinent to the OP's question. “SuperNET will make revenues from the fees its core assets receive, as well as advertising revenue and shared fees with third parties. ... 20 percent for coin communities, according to their proportional contribution” (from https://bitcointalk.org/index.php?topic=762346.0). This might be an interesting idea in principle but I just haven't been able to find any detail. I'd want to know whether that's 20% of net or gross and who maintains the accounting for “advertising revenue and shared fees with third parties”. I'd also want to know how “proportional contribution” is defined and measured in operational terms and the associated accounting calendar. I'll definitely want to know whether there are legal contracts to specify the performance and the full details of the legal entity with whom any contractual relationship is to be established. And that's just from two sentences. Is this all spelled out in detail somewhere? Cheers Graham |
|
|
|
|
Show Posts
