shgraph.hedera-protobuf-java-api.0.55.0.source-code.schedule_sign.proto Maven / Gradle / Ivy
The newest version!
syntax = "proto3";
package proto;
/*-
*
* Hedera Network Services Protobuf
*
* Copyright (C) 2018 - 2021 Hedera Hashgraph, LLC
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*
*/
option java_package = "com.hederahashgraph.api.proto.java";
// <<>> This comment is special code for setting PBJ Compiler java package
option java_multiple_files = true;
import "basic_types.proto";
/**
* Adds zero or more signing keys to a schedule.
*
* If Long Term Scheduled Transactions are enabled and wait_for_expiry was set to true on the
* ScheduleCreate then the transaction will always wait till it's `expiration_time` to execute.
*
* Otherwise, if the resulting set of signing keys satisfy the
* scheduled transaction's signing requirements, it will be executed immediately after the
* triggering ScheduleSign.
*
* Upon SUCCESS, the receipt includes the scheduledTransactionID to use to query
* for the record of the scheduled transaction's execution (if it occurs).
*
* Other notable response codes include INVALID_SCHEDULE_ID, SCHEDULE_ALREADY_DELETED,
* SCHEDULE_PENDING_EXPIRATION, SCHEDULE_ALREADY_EXPIRED,
* INVALID_ACCOUNT_ID, UNRESOLVABLE_REQUIRED_SIGNERS,
* SOME_SIGNATURES_WERE_INVALID, and NO_NEW_VALID_SIGNATURES. For more information
* please see the section of this documentation on the ResponseCode enum.
*/
message ScheduleSignTransactionBody {
/**
* The id of the schedule to add signing keys to
*/
ScheduleID scheduleID = 1;
}